On 5/3/06, Rudolph <[EMAIL PROTECTED]> wrote: > > Nice fix. I found one problem. When a user "forgets" to set the > OneToOneField and saves the object, Django does not return a nice error > message but throws an exception because Django tries to insert a record > without the primary key set. Some kind of validation should be added to > prevent this. Shall I file a ticket?
Please do. I'll look at it, but I might not get to it until the weekend. If anyone else wants to have a look, feel free. Thanks for the catch. I had a nagging feeling there were some corner cases I was missing. Joseph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
