#17957: ORM do not respect null=False if default db engine
interprets_empty_strings_as_nulls
-------------------------------------+-------------------------------------
Reporter: bhuztez | Owner: nobody
Type: Bug | Status: reopened
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by bhuztez):
Replying to [comment:3 ramiro]:
> Replying to [comment:2 bhuztez]:
> > > Does the fact that you are running sql sites with the
--database=other switch affect the outcome of the tests you are performing
or can the example be simplified even more by removing that noisy moving
part?
> > I run the same command `python manage.py sql sites --database=other`
before and after the switch.
> >
>
> That's clear. What I want to know is if there is any particular reason
you are modifying the backend associated with the 'default' DB connection
but then you are running the 'sql' management command specifying the
'other' DB connection. Has the latter any influence of the outcome of the
issue you are seeing?
The outcome of sql command for 'other' DB, is affected by what you set for
{{{DATABASES['default']['ENGINE']}}}.
> Also, this is part of by design, documented behavior of Django CHAR-
based model fields that include '' among the possible valid values when
using Oracle to accommodate particular characteristics of such RDBMS.
This corner case is not documented, AFAIK.
--
Ticket URL: <https://code.djangoproject.com/ticket/17957#comment:5>
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.