#17957: ORM do not respect null=False if default db engine
interprets_empty_strings_as_nulls
-------------------------------------+-------------------------------------
Reporter: bhuztez | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: SVN
(models, ORM) | Resolution: needsinfo
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by ramiro):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
We'd need some clarifications to understand and the decide what to do with
this issue. Particularly:
* What do you mean when you say ''"default db engine"''.
* What did you really do? Change the DB backend used to the Oracle
backend or to the dummy backend?
* Did you change the backend used in both ''default'' and ''other''
aliases?. If not, in which of them?
* Why are you messing with the dummy backend and with the
`interprets_empty_strings_as_nulls` feature.
* Does the fact that you are running ``sql sites`` with the
``--database=other``or can the example be simplified even more by removing
that noisy moving part?
Reopen the ticket when you can provide us that information.
--
Ticket URL: <https://code.djangoproject.com/ticket/17957#comment:1>
Django <https://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.
