#20200: Oracle Inconsistencies with NVARCHAR2 and NCLOB
-------------------------------------+-------------------------------------
Reporter: deejross | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.5
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: oracle | Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shai):
* cc: shai@… (added)
* needs_docs: 0 => 1
* needs_tests: 0 => 1
Comment:
Hi,
References to the conversations about switching nvarchar2 to varchar2 may
be nice here. I haven't seen any such conversations lately, and I don't
think I'd like Django deciding that it's ok to have strings that don't fit
into fields (when the database CHARSET is not unicode).
W.r.t the patch: Especially given the claim that you are not doing an
enhancement, but fixing a bug, please add a test that fails without your
fix, and passes with it (I am not a core committer, and as I said, I am
against your fix, but without tests and a documentation note about the
change, the patch shouldn't even be considered by core).
--
Ticket URL: <https://code.djangoproject.com/ticket/20200#comment:3>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
