On Fri, May 9, 2008 at 7:17 AM, Ziling Zhao <[EMAIL PROTECTED]> wrote: > I filled a bug here about multi-table inheritance problems and fixtures: > http://code.djangoproject.com/ticket/7202 > > In the case that it is valid, I decided to look through the core code to see > where a fix could be placed. > I've looked through it for a bit and it seems like it makes the most sense > in .save() but I'm unsure of that. > > Does fixing it in model.save() makes the most sense?
It depends on exactly what the problem is. I haven't looked into the problem in detail, but I'd be surprised if the solution lies in model.save(). You have encountered this problem as part of the deserialization process. The only way that the solution will lie in model.save() is if you have found a problem with model saving itself - i.e., the problem isn't with deserialization, but with the way models are saved. The test for this - is it possible to generate this error _without_ using loaddata? Can you stimulate the same error with normal "object.property = foo; object.save()" calls? If the answer is yes, then the solution may lie in model.save(). Otherwise, you'll be looking in the deserializer (or serializer) for the solution. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
