The problem with fixtures in documented on the django-mptt page on Google code. There is a patch you need to apply to get them to work. The patch is not necessary for Trunk, however django-mptt does not work on trunk, as too much has changed - in particular, signals.
I would really caution you about this package. Too much magic. Dynamic model changes are highly problematic. Their custom manger does a lot of stuff in raw SQL (by necessity - it would be way to slow to use the ORM). Plus, it's very easy to break things if you are not very careful to use their custom manager for your query operations. mptt is great, but you should really understand what is going on before using this package. On Sep 3, 2008, at 9:57 AM, pihentagy wrote: > > Hi all! > > Has anybody tried to load a fixture to a model class, which is > registered with mptt? > > I tried and failed, all the internal columns need to be filled. > Has anybody a solution how to dump and/or restore such tables? > > thanks > Gergo > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
