On Tue, 2007-05-15 at 17:01 -0500, Jeremy Dunck wrote: > On 5/15/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > One solution would be that the model field only stores the pickled > > value. > > I think it's not well understood that model fields can be created by > subclassing django.db.models.fields.Field.
True, although I wasn't actually suggesting a Field subclass (I'm aware that's not well documented yet, but that's partly because it's missing some machinery to make it truly useful). I was suggesting adding a property to the Model class that acted as a proxy for the CharField or whatever is being used to store the pickled value. > Lucki, have a look at the docstrings in that class (in file > django/db/models/fields/__init__.py). They're pretty descriptive; > look at FileField for an example of a field that does a fair bit of > non-vanilla customization. Creating a Field sub-class is certainly another option, you're right. One day I'll have the infinite spare time I've been asking Santa Claus for and maybe get around to adding the missing pieces and documentation. Or somebody will beat me to it (even better). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
