Hi, On 4/26/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Wow .. there's been a lot of response to this without the answer > actually appearing: it's a bug! :-) > > Ticket #3774 is the relevant ticket. > > I'm very tempted to fix this by actually implementing the documented > behaviour, because it makes a lot of sense. My only caution so far has > been that it's a backwards compatible change and anybody inadvertently > relying on the current behaviour (and you can see from one of my > comments in that ticket that I don't consider it completely illogical to > allow blanks there, so it's not a crazy assumption) would have to change > things.
In which case it is a good think to let the primary_key field empty? If I add an entry with my primary key field empty I just cannot delete it in the admin (because there is no link to click on). Maybe there are cases which this could be useful.. but I cannot imagine one of them... > I keep tossing this one around in my head, but it will be fixed one way > or another soon, I would expect (either by me or another developer). Thanks Kai --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
