Here's my example then:
class Property(models.Model):
class Admin:
pass
showGone = models.BooleanField(default=False)
goneGroup = models.CharField(maxlength=100)
def save(self):
""" save, but set id to 1 """
self.id=1
super(Property, self).save()
[EMAIL PROTECTED] wrote:
> No you dont need a different table for each property, one table stores
> all the properties that you want to collect together.
>
> The problem with the (name,value) approach is that all the values have
> to be the same type, so you cant present some properties as text, s
No you dont need a different table for each property, one table stores
all the properties that you want to collect together.
The problem with the (name,value) approach is that all the values have
to be the same type, so you cant present some properties as text, some
as boolean, and some as drop-d
[EMAIL PROTECTED] wrote:
> I wanted a way to store 'properties' - single values over an app (or
> project) that control the apps behaviour, for example a title to appear
> on the page, or whether to display threads expanded or not in a forum.
> I thought it would be nice to have these settings con
I wanted a way to store 'properties' - single values over an app (or
project) that control the apps behaviour, for example a title to appear
on the page, or whether to display threads expanded or not in a forum.
I thought it would be nice to have these settings configurable from the
Admin interfac
