On 11/23/07, Patryk Zawadzki <[EMAIL PROTECTED]> wrote: > > 2007/11/23, Rudolph <[EMAIL PROTECTED]>: > > > > Structured markup can only represent tree like organised objects > > (without tricks). Maybe we can keep the primary keys inside the > > fixtures, but add an optional attribute that indicates that the > > primary key for this object is only used to link the objects together > > when importing the data?
Personal preference would be for this to be a command option, rather than a permanent part of the fixture. > So just add and implement pk_key="discard" as parameter inside a > fixture? Then the ids are only relevant in the context of matching > them inside that particular fixture. ... and now we come to the reason why this hasn't been implemented previously :-) Just to be clear - I am in favour of 'pk-less' fixtures at a conceptual level - we just need to make the concept work. This issue that you have identified here is the biggest stumbling block. If you can find a clean way to make this work, you're home. 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 django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
