On Thu, Aug 5, 2010 at 3:44 PM, Xavier Ordoquy <xordo...@linovia.com> wrote: > Hi Russ, > > Indeed, my investigations have lead me to #14025 which fixed the major issue. > > If I remember correctly the corrupted file part was due to the fact that I > was still using an "old style" fixture filename - ie <name>.json instead of > <name>.<database name>.json with data on both databases. > If you find it useful, I can investigate further about this message and make > a patch in order to output an appropriate message.
"Old style" fixture names should still be valid -- if a database name isn't specified, the fixture will be loaded on all available databases. If you've got a test case where this fails, it should be reported. Yours, Russ Magee %-) -- 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.
