If I remember correctly, my problem was that the JSON serializer was bombing out when encountering float fields. I didn't report it directly because I thought I had remembered seeing others report similar problems. It was probably a late night and I got around it by opting for XML formatting.
Thanks for the update Russell, nice to see the aggressive work being put into this very useful aspect of the framework. Cheers -Brian On Apr 11, 5:22 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On 4/12/07, Merric Mercer <[EMAIL PROTECTED]> wrote: > > > > > I tried to run the dumpdata command because I'd read that this did much > > of the work for me but I received the following error message > > > >>C:\>manage.py dumpdata promotions > > Unable to serialize database: Table_Code matching query does not exist. > > None > > This sounds like your database isn't fully synchronized. Try > recreating your database from scratch, resyncing, then dumping the > data. > > > My models have several 1:1 relationships and I think I remember seeing > > something about this causing a problem in the test framework - but I > > can't relocate the post that mentioned this. Does anybody know the > > status on this? > > As far as I am aware, these problems have been solved. We now have a > very extensive set of unit tests to check the full range of data > parsing - if you find a case that is failing, let us know so we can > fix the problem and add another test. > > 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 [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-users?hl=en -~----------~----~----~----~------~----~------~--~---
