#9862: Non-standard SQL generated in column definition for nullable columns in
create table DDL
------------------------------------+---------------------------------------
Reporter: Ambrish | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Accepted
Comment:
No database on earth implements the same subset of SQL, so references to
the standard, with all its optional bits and non-standard extensions in
implementation, isn't too helpful either way. However, if a database
doesn't support something, we should make sure it's not required. Practice
always trumps theory.
In this case, the solution is probably just to not include the `NULL`.
`NOT NULL` is permitted, so we include that for `null=False` fields and
use the fact that columns should be nullable by default.
Ambrish: it's only `NULL` that is causing a problem on db2, right? `NOT
NULL` is fine?
We still need to check that this works sufficiently on all the other
backends (including getting some confirmation from Ramiro Morales about MS
SQL). If there's an inconsistency in requirements, it will need an
addition of another `BaseDatabaseFeature` function.
--
Ticket URL: <http://code.djangoproject.com/ticket/9862#comment:1>
Django <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
-~----------~----~----~----~------~----~------~--~---
