#5671: Change SQL generation when primary_key=True and unique=True
-------------------------------------------------+--------------------------
Reporter: Nis Jørgensen <[EMAIL PROTECTED]> | Owner:
nobody
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------------------+--------------------------
Changes (by Nis Jørgensen <[EMAIL PROTECTED]>):
* needs_better_patch: => 0
* has_patch: 0 => 1
* needs_tests: => 0
* needs_docs: => 0
Comment:
Oops - double submit. The patches are identical.
The patch does the following:
If a field is declared as primary_key, it is automatically flagged as
unique
If a field is declared as primary_key, no UNIQUE is output in the SQL.
All checks of the type
{{{
if f.primary_key or f.unique:
}}}
are replaced by
{{{
if f.unique:
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/5671#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
