Hi All, I've just created two new tickets - #3389 and #3390.
http://code.djangoproject.com/ticket/3389/ http://code.djangoproject.com/ticket/3390/ They both have patches attached, but the ideas are not completely trivial, so I thought I'd throw them out for comment before I did anything damaging to the trunk. They are both related to deserialization, which, in turn, have an effect on the fixtures system (see #2333). In short, the existing deserializer can't handle foward or circular references (which is to say, just about any interesting data set for testing purposes). The two patches combine to fix the problem. Specific details are on the tickets. #3390 describes the changes to the deserializer, including some model definition changes that are required for Postgres (and, I suspect, Oracle). #3389 describes a minor extension to m2m relations required by the deserializer change. This change pretty much mirrors the type of assignments that are already possible with m2o relations; I can't work out if the disparity is by design, or by accident. Comments? Feedback? On a related note, I have been using JSON pretty much exclusively for this testing (as evidenced by the unit tests attached to these tickets), but my initial inspection leads me to believe that an analogous problem exists with the XML serializer. If the approach described in these tickets is approved, I'll make the changes for the XML side, too (along with some badly needed regression tests for both serializer backends). Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
