So I'm not missing anything. It's a bug. Ouch... Thanks for the info, before I trawled my way through the serializers. May well have to apply the patch locally to move forward. There doesn't seem to be much movement on the ticket.
On Nov 15, 1:40 pm, "Alex Koshelev" <[EMAIL PROTECTED]> wrote: > There is ticket and patch for this > issuehttp://code.djangoproject.com/ticket/9522 > > On Sat, Nov 15, 2008 at 16:38, AndyH <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I have a custom model field class that stores event recurrence > > information. In python this is an instance of dateutil.rrule.rule, and > > in the database I am storing it as an iCal recurrence string. To > > convert between these two formats I have to_python and > > get_db_prep_value methods on the custom field class (subclassing > > models.Field). > > > Things works more-or-less OK, but when I run dumpdata to serialize the > > database into json, at some point to_json gets executed and the > > returned value for rrule is '<dateutil.rrule.rrule instance at > > 0x1121828>' and not the value that should be returned by > > get_db_prep_value. I also have a 'value_to_string' method on the > > fiels, but this does not get executed either. > > > What am I missing about the way dumpdata handles these custom model > > fields? > > > Thanks > > Andy. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
