Re: .save() works with no (custom, not 'id') primary key specified?

On Fri, Apr 29, 2011 at 12:17 PM, Jeff Blaine <cjblaine@gmail.com> wrote:
> "primary_key=True implies null=False and unique=True. Only one primary key
> is allowed on an object."
> So that unique=True part is inaccurate?  Or is that, again, another thing
> that will fail only at validation?

did you test pass more than once?

check the saved object(s?), is the primary key field a zero string, or
NULL? most databases consider NULL non-equal to any value, including
other NULLs, and allow multiple records with NULLs in a unique field.

also, some databases consider the zero string a valid representation
for NULL. which RDBMS are you using?

--
Javier

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.