On 12/17/06, Fernando Gutierrez <[EMAIL PROTECTED]> wrote: > > This also excludes the integer 0 that evaluates to False. That is a > problem, some legacy databases use 0 as the first pk for some tables, in > that case you can't modify the objects that have this primary key.
Ok; ticket #2160 is two problems. Firstly, the logic error in the documentation; this has now been fixed. The fact that you can't use 0 as a pk value is a separate problem. This strikes me as a problem that should be fixed, not just documented. I've revised the ticket description for #2160 to reflect the remaining problem. 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 [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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
