delta/python-packages/sqlalchemy.git/lib/sqlalchemy/dialects, branch pr/72 github.com: zzzeek/sqlalchemy.git Fix unique constraints reflection in SQLite 2014-02-14T12:09:21+00:00 Roman Podoliaka rpodolyaka@mirantis.com 2014-02-14T11:04:57+00:00 a7e0d3e1e36076e20ead9447508d99b2e477ba46 Reflection of unique constraints didn't work properly, if reserved identifiers had been used as column names. In this case column names would be put in double quotes (e.g. the name of column asc would be returned as "asc"). This issue is only present in 0.8.4 and not in 0.9.x. 
Reflection of unique constraints didn't work properly, if reserved
identifiers had been used as column names. In this case column names
would be put in double quotes (e.g. the name of column asc would be
returned as "asc").

This issue is only present in 0.8.4 and not in 0.9.x.
- Fixed bug which prevented MySQLdb-based dialects (e.g. 2014-02-03T17:06:57+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-02-03T17:04:51+00:00 cd1baf6572baa31230e88624b7e5df87608d01c7 pymysql) from working in Py3K, where a check for "connection charset" would fail due to Py3K's more strict value comparison rules. The call in question wasn't taking the database version into account in any case as the server version was still None at that point, so the method overall has been simplified to rely upon connection.character_set_name(). [ticket:2933] 
pymysql) from working in Py3K, where a check for "connection
charset" would fail due to Py3K's more strict value comparison
rules.  The call in question  wasn't taking the database
version into account in any case as the server version was
still None at that point, so the method overall has been
simplified to rely upon connection.character_set_name().
[ticket:2933]
- add a few missing methods to the cymysql dialect 2014-02-02T23:21:09+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-02-02T23:16:17+00:00 2ac2bbd3508843a200b6245225bef3bc4631fb41 






- apply a similar fix for floats to mssql+pyodbc as we did to firebird
2013-12-28T22:51:51+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-12-28T22:50:19+00:00

a1d2e4d4915544b0257d294f4a92fb904fbf1a6b

- wrangle through osx+pyodbc+freetds to get at least test_suite to pass again
with mssql+pyodbc. invovled adding some silly requirements





- wrangle through osx+pyodbc+freetds to get at least test_suite to pass again
with mssql+pyodbc. invovled adding some silly requirements







- The firebird dialect will quote identifiers which begin with an
2013-12-27T18:42:43+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-12-27T18:40:27+00:00

c24e825c37d9f1f33fa4c1722c945aea26a1fc11

underscore.  Courtesy Treeve Jelbert. [ticket:2897]





underscore.  Courtesy Treeve Jelbert. [ticket:2897]







- Fixed bug in Firebird index reflection where the columns within the
2013-12-27T18:42:28+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-12-27T18:20:58+00:00

320bc4861ccd390a0e3871231542620ab33dfa21

index were not sorted correctly; they are now sorted
in order of RDB$FIELD_POSITION.





index were not sorted correctly; they are now sorted
in order of RDB$FIELD_POSITION.







- The "asdecimal" flag used with the :class:`.Float` type will now
2013-12-27T18:41:46+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-12-27T18:16:48+00:00

b5b84ae20d186fc82fcba453626fe33cce5ef96b

work with Firebird dialects; previously the decimal conversion was
not occurring.
- scale back some firebird FP numeric tests

Conflicts:
	test/requirements.py





work with Firebird dialects; previously the decimal conversion was
not occurring.
- scale back some firebird FP numeric tests

Conflicts:
	test/requirements.py







Remove terminated connections from the pool.
2013-12-27T16:14:21+00:00

John Anderson
sontek@gmail.com

2013-12-16T20:50:10+00:00

4211207abfd96ddc06e37418d3a2132bd8ca89d8

In pymssql, if you terminate a long running query manually
it will give you a connection reset by peer message, but this
connection remains in the pool and will be re-used.





In pymssql, if you terminate a long running query manually
it will give you a connection reset by peer message, but this
connection remains in the pool and will be re-used.







Fix MSSQL dialects visit_drop_index to use the correct DDL
2013-12-05T23:37:50+00:00

donkopotamus
derek.harland@finq.co.nz

2013-12-05T03:49:13+00:00

2f18f9b2f5f354421986d5e16793ca663d1fb14c












- backport unique constraints reflection to 0.8.4, thereby
2013-12-03T19:59:50+00:00

Roman Podolyaka
roman.podolyaka@gmail.com

2013-06-09T16:07:00+00:00

e8458ab96b1bda5f139d34a24808167dd1f590c6

assisting with alembic installations that have upgraded and are dealing with
PG index/unique constraint reflection.

Inspection API already supports reflection of table
indexes information and those also include unique
constraints (at least for PostgreSQL and MySQL).
But it could be actually useful to distinguish between
indexes and plain unique constraints (though both are
implemented in the same way internally in RDBMS).

This change adds a new method to Inspection API - get_unique_constraints()
and implements it for SQLite, PostgreSQL and MySQL dialects.





assisting with alembic installations that have upgraded and are dealing with
PG index/unique constraint reflection.

Inspection API already supports reflection of table
indexes information and those also include unique
constraints (at least for PostgreSQL and MySQL).
But it could be actually useful to distinguish between
indexes and plain unique constraints (though both are
implemented in the same way internally in RDBMS).

This change adds a new method to Inspection API - get_unique_constraints()
and implements it for SQLite, PostgreSQL and MySQL dialects.