Tried it out. Interestingly, natural keys are currently used only for foreign key references, the dump still contains primary keys. Looks like there's a patch for leaving out PK's when natural keys are used: http://code.djangoproject.com/ticket/13252 That would get me 100% of the way there.
- PW On Oct 22, 12:38 pm, Paul Winkler <sli...@gmail.com> wrote: > Thanks Shawn! That was quick! > > Meanwhile I just discoveredhttp://farmdev.com/projects/fixturewhich > I have just confirmed works fine for hand-written fixtures with my > app, although using python classes as fixtures feels a little odd. > Nice that it's cross-platform though, it supports sqlalchemy and > sqlobject and appengine as well as django. > > It looks like using Django 1.2's built-in natural keys support will be > a lot less work in many situations, since Fixture doesn't (yet) have > support for dumping existing Django data to a file. > Going to try natural keys! > > - PW > > On Oct 22, 11:56 am, Shawn Milochik <sh...@milochik.com> wrote: > > > And like magic, it's there! > > >http://docs.djangoproject.com/en/dev/topics/serialization/#natural-keys > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
