#26683: Oracle DBs: Add option to use VARCHAR2 data type --------------------------------+-------------------------------------- Reporter: elarandjelovic | Owner: nobody Type: New feature | Status: new Component: Migrations | Version: 1.9 Severity: Normal | Resolution: Keywords: Oracle | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 --------------------------------+--------------------------------------
Comment (by shaib): A few points: 1) Oracle 11.2 "extended support" is until 2020. We may decide to drop our support of 11.2 earlier, but that wouldn't be nice to our users. 2) Varchar vs. NVarchar performance issues are well documented; such an issue was [https://sourceforge.net/p/cx-oracle/mailman/message/35134630/ raised] only a few hours ago on the cx-oracle users group. 3) Actually, if anyone has the time to put into it, a compatibility- breaking new Oracle backend could have a lot of benefits -- two important problems that are hard to fix in a backward-compatible manner are the performance issues around numbers (we translate many numbers to strings in order to figure out the right Python type) and the case issues around database object (tables etc) names. -- Ticket URL: <https://code.djangoproject.com/ticket/26683#comment:14> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/072.1cfc067082b4441ae7a42c8281e622a6%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.