summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* Add missing import that caused test_notice_logging to fail if this suite was ↵Chris Withers2013-05-261-0/+1
| | | | run on its own.
* Fixed a bug where the routine to detect the correct kwargsMike Bayer2013-05-231-2/+22
| | | | | | being sent to :func:`.create_engine` would fail in some cases, such as with the Sybase dialect. [ticket:2732]
* Regression from this ticket caused the unsupported keywordMike Bayer2013-05-152-0/+21
| | | | | | "true" to render, added logic to convert this to 1/0 for SQL server. [ticket:2682]
* Fixed a regression from 0.7 caused by this ticket, whichMike Bayer2013-05-131-0/+54
| | | | | | | | made the check for recursion overflow in self-referential eager joining too loose, missing a particular circumstance where a subclass had lazy="joined" or "subquery" configured and the load was a "with_polymorphic" against the base. [ticket:2481]
* - cleanupMike Bayer2013-05-051-17/+20
| | | | - move the timeout here to 14 seconds as jenkins still chokes occasionally
* cleanupMike Bayer2013-05-041-32/+60
|
* cleanupMike Bayer2013-05-041-79/+78
|
* cleanupMike Bayer2013-05-041-67/+68
|
* formatting stuffMike Bayer2013-05-041-49/+51
|
* - disable tests failing with pypy2, [ticket:2719]Mike Bayer2013-05-012-2/+6
|
* - Fixed a regression from 0.7 where the contextmanager featureMike Bayer2013-04-301-1/+63
| | | | | | | of :meth:`.Session.begin_nested` would fail to correctly roll back the transaction when a flush error occurred, instead raising its own exception while leaving the session still pending a rollback. [ticket:2718]
* missing commaMike Bayer2013-04-301-2/+2
|
* Updated mysqlconnector dialect to check for disconnect basedMike Bayer2013-04-291-13/+6
| | | | | on the apparent string message sent in the exception; tested against mysqlconnector 1.0.9.
* the callcount went up here, still less than with no C extensions, not preparedMike Bayer2013-04-261-7/+7
| | | | to worry about it too much
* Fixes to the ``sqlalchemy.ext.serializer`` extension, includingMike Bayer2013-04-261-28/+44
| | | | | | | that the "id" passed from the pickler is turned into a string to prevent against bytes being parsed on Py3K, as well as that ``relationship()`` and ``orm.join()`` constructs are now properly serialized. [ticket:2698] and some other observed issues.
* and a lot of tests. five fail without the changeMike Bayer2013-04-261-0/+264
|
* everything passes with this!!!!!!! holy crap !!!!! and its the simplest of allMike Bayer2013-04-251-20/+83
|
* - attempt to replace the whole idea of "join_to_left" with a moreMike Bayer2013-04-241-2/+2
| | | | | fundamental and general purpose heuristic. this initial approach has about 60 tests failing but seems to have gone pretty far
* break into multiple testsMike Bayer2013-04-241-7/+98
|
* formattingMike Bayer2013-04-241-47/+48
|
* - merge exists() patch + changelogMike Bayer2013-04-231-0/+15
|\
| * adding convenience method exists() to Query (see # 2673)Diana Clarke2013-03-291-0/+15
| |
* | Fully implemented the IS and IS NOT operators withMike Bayer2013-04-221-1/+28
| | | | | | | | | | | | | | | | | | | | regards to the True/False constants. An expression like ``col.is_(True)`` will now render ``col IS true`` on the target platform, rather than converting the True/ False constant to an integer bound parameter. This allows the ``is_()`` operator to work on MySQL when given True/False constants. [ticket:2682]
* | tweak this some more to handle the array being empty againMike Bayer2013-04-221-0/+11
| |
* | - change to [ticket:2681], pre-coerce the array to listMike Bayer2013-04-221-10/+3
| | | | | | | | unconditonally instead so that it works in all cases.
* | The operators for the Postgresql ARRAY type supportsMike Bayer2013-04-221-60/+106
| | | | | | | | | | | | | | | | | | | | input types of sets, generators, etc. but only when a dimension is specified for the ARRAY; otherwise, the dialect needs to peek inside of "arr[0]" to guess how many dimensions are in use. If this occurs with a non list/tuple type, the error message is now informative and directs to specify a dimension for the ARRAY. [ticket:2681]
* | merge cymysql branchMike Bayer2013-04-211-0/+1
|\ \
| * \ merge from defaultHajime Nakagami2013-04-205-3/+234
| |\ \
| * | | testing.crashes on cymysql >= 0.6Hajime Nakagami2013-04-201-1/+1
| | | |
| * | | skip with cymysql 0.6Hajime Nakagami2013-04-201-0/+1
| | | |
* | | | - Improvements to the operation of the pymysql dialect onMike Bayer2013-04-211-20/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Python 3, including some important decode/bytes steps. Issues remain with BLOB types due to driver issues. Courtesy Ben Trofatter. - start using util.py3k, we will eventually remove the sa2to3 fixer entirely
* | | | Merged in bentrofatter/sqlalchemy-2663 (pull request #49)Mike Bayer2013-04-211-1/+10
|\ \ \ \ | | | | | | | | | | | | | | | Fixed PyMySQL problems for Python 2.x and mitigated some issues with Python 3.x
| * | | | Removed commented line from test_types.pyBen Trofatter2013-03-191-1/+0
| | | | |
| * | | | Added workaround for pymysql3 double wrapping ProgrammingErrors to pymysql ↵Ben Trofatter2013-03-181-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dialect. Added workaround for pymysql3 return a bytes object when queried for isolation level.
* | | | | Fixed bug where many-to-many relationship with uselist=FalseMike Bayer2013-04-211-2/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | would fail to delete the association row and raise an error if the scalar attribute were set to None. Also in 0.7.11. [ticket:2710]
* | | | | - remove lots of old tests here that are coveredMike Bayer2013-04-211-278/+116
| | | | | | | | | | | | | | | | | | | | elsewhere, cleanup
* | | | | - establish ordering here for the hstore repr testMike Bayer2013-04-201-4/+5
| | | | |
* | | | | order the properties here to get the SQL to be deterministicMike Bayer2013-04-201-7/+7
| | | | |
* | | | | - these pickle the assoc proxy by itself tests can't really passMike Bayer2013-04-202-7/+13
| |_|/ / |/| | | | | | | | | | | | | | | now without strong ref on the parent - fix message compare for py3k
* | | | Improved the behavior of instance management regardingMike Bayer2013-04-202-0/+158
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the creation of strong references within the Session; an object will no longer have an internal reference cycle created if it's in the transient state or moves into the detached state - the strong ref is created only when the object is attached to a Session and is removed when the object is detached. This makes it somewhat safer for an object to have a `__del__()` method, even though this is not recommended, as relationships with backrefs produce cycles too. A warning has been added when a class with a `__del__()` method is mapped. [ticket:2708]
* | | | - this pymssql test needs to be against the pymssql dialectMike Bayer2013-04-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Part of a longer series of fixes needed for pyodbc+ mssql, a CAST to NVARCHAR(max) has been added to the bound parameter for the table name and schema name in all information schema queries to avoid the issue of comparing NVARCHAR to NTEXT, which seems to be rejected by the ODBC driver in some cases, such as FreeTDS (0.91 only?) plus unicode bound parameters being passed. The issue seems to be specific to the SQL Server information schema tables and the workaround is harmless for those cases where the problem doesn't exist in the first place. [ticket:2355]
* | | | - test + changelog for [ticket:2691]Mike Bayer2013-04-181-1/+23
| | | |
* | | | - additional test + correction for [ticket:2699]Mike Bayer2013-04-181-1/+52
| |/ / |/| |
* | | Fixed bug whereby ORM would run the wrong kind ofMike Bayer2013-04-111-2/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | query when refreshing an inheritance-mapped class where the superclass was mapped to a non-Table object, like a custom join() or a select(), running a query that assumed a hierarchy that's mapped to individual Table-per-class. [ticket:2697]
* | | - unit test failing on python3.3 + psycopg2, add an order byMike Bayer2013-04-111-1/+1
| | |
* | | Improvements to Connection auto-invalidationMike Bayer2013-04-111-14/+122
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | handling. If a non-disconnect error occurs, but leads to a delayed disconnect error within error handling (happens with MySQL), the disconnect condition is detected. The Connection can now also be closed when in an invalid state, meaning it will raise "closed" on next usage, and additionally the "close with result" feature will work even if the autorollback in an error handling routine fails and regardless of whether the condition is a disconnect or not. [ticket:2695]
* | | A major fix to the way in which a select() object producesMike Bayer2013-04-115-0/+246
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | labeled columns when apply_labels() is used; this mode produces a SELECT where each column is labeled as in <tablename>_<columnname>, to remove column name collisions for a multiple table select. The fix is that if two labels collide when combined with the table name, i.e. "foo.bar_id" and "foo_bar.id", anonymous aliasing will be applied to one of the dupes. This allows the ORM to handle both columns independently; previously, 0.7 would in some cases silently emit a second SELECT for the column that was "duped", and in 0.8 an ambiguous column error would be emitted. The "keys" applied to the .c. collection of the select() will also be deduped, so that the "column being replaced" warning will no longer emit for any select() that specifies use_labels, though the dupe key will be given an anonymous label which isn't generally user-friendly. [ticket:2702]
* | | order by...Mike Bayer2013-04-091-2/+2
| | |
* | | Fixed indirect regression regarding :func:`.has_inherited_table`,Mike Bayer2013-04-091-1/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | where since it considers the current class' ``__table__``, was sensitive to when it was called. This is 0.7's behavior also, but in 0.7 things tended to "work out" within events like ``__mapper_args__()``. :func:`.has_inherited_table` now only considers superclasses, so should return the same answer regarding the current class no matter when it's called (obviously assuming the state of the superclass). [ticket:2656]
* | | Fixed bug when a query of the form:Mike Bayer2013-04-092-0/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``query(SubClass).options(subqueryload(Baseclass.attrname))``, where ``SubClass`` is a joined inh of ``BaseClass``, would fail to apply the ``JOIN`` inside the subquery on the attribute load, producing a cartesian product. The populated results still tended to be correct as additional rows are just ignored, so this issue may be present as a performance degradation in applications that are otherwise working correctly. [ticket:2699]
View Lorry Controller Status