On 3/13/07, Chris Moffitt <[EMAIL PROTECTED]> wrote: > > Russell Keith-Magee wrote: > > Can you provide a specific example? Like I said, I'm adding a unit > > test to cover all the edge cases of serialization - if you have a > > specific example that is failing, I'd like to make sure that your > > example is covered in the test. > > > > > You hit it. It was a One to One field that was causing the problem. > > Now, I'm moving on to another problem when I try to load the data. I > have a place where it thinks there is a Null value but I don't know > where it is having problems. I'd suggest that it display a little more > info about where the problem is, instead of this somewhat vague error- > > ['This field cannot be null.'] > > Since I have quite a few fields, it would be helpful if it told me what > field or atleast which model it was getting stuck on.
Hrm. The test case checks Null values for every data field, so that shouldn't be a problem. The only simple reason I can think of is a required field that doesn't have a representation in your data file. How are you producing your data file? Is this failure caused by a data file produced by dump, or is it manually created? Can you provide a small fixture file (and model) that exhibits the problem? 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-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 -~----------~----~----~----~------~----~------~--~---
