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. 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
