| Age | Commit message (Collapse) | Author |
|
Thanks thevlad at gmail.com for the report.
Backport of 89116cf24a from master.
|
|
Thanks k_sze for the report.
Backport of 67c6c1a7c from master.
|
|
and how to prevent table-name truncation
Thanks russellm & timo for discussion, and timo for review.
Backported from master 317040a73b77be8f8210801793b2ce6d1a69301e
|
|
permission on SYS.DBMS_LOB.
Thanks jafula for the suggestion.
Backport of a86ecc80a2 from master
|
|
AUTO_INCREMENT values.
Thanks kent at nsc.liu.se for the report.
Backport of c54fa1a7bc from master
|
|
The documentation and comments now all use 'an' to
refer to the word SQL and not 'a'.
Backport of 4d13cc56de from master
|
|
+ Removed a reference about MySQL storage engines also being
called 'table types', as this term has been deprecated for
8 years and is no longer used.
+ Fixed the link to the official InnoDB storage engine docs.
+ Apache (versions >= 2.4) will always choose a multi-threaded
MPM module on modern operating systems (later than 2002).
Backport of fa217d14a0 from master
|
|
Add support for Oracle, fix an issue with the repr of RawQuerySet,
add tests and documentations. Also added a 'supports_paramstyle_pyformat'
database feature, True by default, False for SQLite.
Thanks Donald Stufft for review of documentation.
|
|
|
|
Thanks tinodb for the report.
|
|
It took me quite some time to find if and where the ODBC backend was maintained.
I found (on djangoproject.com):
http://code.google.com/p/django-pyodbc/ (last commit about 3 years ago)
then:
https://github.com/avidal/django-pyodbc avidal fork.
then:
https://github.com/aurorasoftware/django-pyodbc/ aurorasoftware version which has avidal improvements merged.
Avidals version now links to https://github.com/aurorasoftware/django-pyodbc/ which is also the version installed through PIP.
|
|
|
|
Current ports of MySQLdb are very buggy in this area.
|
|
Made a few minor compatibility adjustments.
|
|
Refs #20104.
|
|
MySQL accepts 0000-00-00 as a valid date but MySQLdb converts those
values into None. So there will be problems for instance if trying to
transport the data using dumpdata/loaddata.
This patch refs #6642 that has been closed as wontfix since this is a
particular problem of MySQL.
|
|
|
|
Technically speaking they aren't usable yet.
|
|
This is mostly a documentation change.
It has the same backwards-incompatibility consequences as those
described for PostgreSQL in a previous commit.
|
|
Thanks limscoder for the report and niwi for the draft patch.
|
|
Thanks Anssi Kääriäinen and Karen Tracey for their inputs.
|
|
Added -n to sphinx builds to catch issues going forward.
|
|
|
|
|
|
Thanks Melevir for the patch.
|
|
|
|
Thanks philipn for the report and mateusgondim for the patch.
|
|
* Renamed smart_unicode to smart_text (but kept the old name under
Python 2 for backwards compatibility).
* Renamed smart_str to smart_bytes.
* Re-introduced smart_str as an alias for smart_text under Python 3
and smart_bytes under Python 2 (which is backwards compatible).
Thus smart_str always returns a str objects.
* Used the new smart_str in a few places where both Python 2 and 3
want a str.
|
|
|
|
database creation.
|
|
|
|
Thanks Florian Apolloner for the patch.
|
|
Fixed #17957 -- when using Oracle and character fields, the fields
were set null = True to ease the handling of empty strings. This
caused problems when using multiple databases from different vendors,
or when the character field happened to be also a primary key.
The handling was changed so that NOT NULL is not emitted on Oracle
even if field.null = False, and field.null is not touched otherwise.
Thanks to bhuztez for the report, ramiro for triaging & comments,
ikelly for the patch and alex for reviewing.
|
|
using MySQL+MyISAM.
Refs #15507, #18116 and r17341, r17921.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17923 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
Thanks Carl, Claude and Anssi for discussion and patch review.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17921 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
the initial patch and Aymeric Augustin for the review.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17834 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17703 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17630 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
engine. Thanks Lenz Hirsch for the report and Claude Paroz for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17552 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
isn't necessary.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17194 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
foreign keys.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17120 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
conceive of a time unit smaller than a second. Thanks jammon and poirier.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17095 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16987 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16984 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
[16955]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16983 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
casual relationship with sanity. Thanks to Jim Dalton for the report and patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16787 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
This was still causing some confusion, so I rewrote the section in the
database notes to encompass both substring matching and non-ASCII
case-insensitive equality checks, as well as putting in a stronger
callout on the "contains" filter.
Refs #16569.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16694 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
database backend list. Thanks to Mike Hagman and melinath.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16624 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
database backends (such as MySQL/InnoDB) that do not support deferred constraint checking. Many thanks to jsdalton for coming up with a clever solution to this long-standing issue, and to jacob, ramiro, graham_king, and russellm for review/testing. (Apologies if I missed anyone else who helped here.)
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16590 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|
|
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16423 bcc190cf-cafb-0310-a4f2-bffc1f526a37
|