6 Commits

Author	SHA1	Message	Date
Shai Berger	cf159e5c93	Fix get_or_create test failure under Oracle ... Test expected that when given invalid utf-8, the backend should raise a DatabaseError, but the Oracle backend raises a UnicodeDecodeError.	2013-05-26 01:39:34 +03:00
Aymeric Augustin	0e51d8eb66	Fixed #20463 -- Made get_or_create more robust. ... When an exception other than IntegrityError was raised, get_or_create could fail and leave the database connection in an unusable state. Thanks UloPe for the report.	2013-05-22 10:56:06 +02:00
Alex Gaynor	7c56212c71	Lower the max length for a test field so that it works on MySQL.	2013-05-19 13:58:58 -07:00
Pablo Recio	65f9e0affd	Fixes #18896. Add tests verifying that you can get IntegrityErrors using get_or_create through relations like M2M, and it also adds a note into the documentation warning about it	2013-05-19 14:16:12 +02:00
Aymeric Augustin	3a4276ffc3	Tested that get_or_create raises IntegrityError. ... It used to raise "DatabaseError: no such savepoint" with the old transaction management. Closes #15117.	2013-04-28 17:15:41 +02:00
Florian Apolloner	89f40e3624	Merged regressiontests and modeltests into the test root.	2013-02-26 14:36:57 +01:00