#3390: Deserializer cannot handle circular and forward references to object
instances
--------------------------------------------------------------------------+-
   Reporter:  russellm                                                    |     
           Owner:  jacob                 
     Status:  new                                                         |     
       Component:  Serialization         
    Version:  SVN                                                         |     
      Resolution:                        
   Keywords:  JSON deferrable deserialization circular forward reference  |     
           Stage:  Design decision needed
  Has_patch:  1                                                           |     
      Needs_docs:  0                     
Needs_tests:  0                                                           |   
Needs_better_patch:  1                     
--------------------------------------------------------------------------+-
Comment (by mtredinnick):

 I don't like this solution. Until now, the serializer provided a nice way
 to move data between Django installations: I could email somebody the
 serialised output and they could run it as an addition to their database.
 Or I could save it away and use it later after arbitrary things have
 happened in my database. But you can't do that if you also want to control
 the primary key values, because it may clash with existing ones.
 
 I think we need to be smarter here, if we can.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3390#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to