delta/python-packages/sqlalchemy.git/lib/sqlalchemy/dialects, branch pr/47

- Fixed bug where index reflection would mis-interpret indkey values

2013-10-27T22:16:42+00:00

when using the pypostgresql adapter, which returns these values
as lists vs. psycopg2's return type of string.
[ticket:2855]

Conflicts:
	doc/build/changelog/changelog_09.rst
	lib/sqlalchemy/__init__.py

- Fixed bug where Oracle table reflection using synonyms would fail

2013-10-25T23:12:17+00:00

if the synonym and the table were in different remote schemas.
Patch to fix courtesy Kyle Derr. [ticket:2853]

- attempt to clarify what mutable extension does for HSTORE, [ticket:2803]

2013-10-18T23:35:22+00:00

- Removed a 128-character truncation from the reflection of the

2013-10-18T23:00:29+00:00

server default for a column; this code was original from
PG system views which truncated the string for readability.
[ticket:2844]

- The change in :ticket:`2721`, which is that the ``deferrable`` keyword

2013-10-18T19:00:42+00:00

of :class:`.ForeignKeyConstraint` is silently ignored on the MySQL
backend, will be reverted as of 0.9; this keyword will now render again, raising
errors on MySQL as it is not understood - the same behavior will also
apply to the ``initially`` keyword.  In 0.8, the keywords will remain
ignored but a warning is emitted.   Additionally, the ``match`` keyword
now raises a :class:`.CompileError` on 0.9 and emits a warning on 0.8;
this keyword is not only silently ignored by MySQL but also breaks
the ON UPDATE/ON DELETE options.

To use a :class:`.ForeignKeyConstraint`
that does not render or renders differently on MySQL, use a custom
compilation option.  An example of this usage has been added to the
documentation, see :ref:`mysql_foreign_keys`.
[ticket:2721] [ticket:2839]

MySQL-connector dialect now allows options in the create_engine

2013-10-13T18:09:53+00:00

query string to override those defaults set up in the connect,
including "buffered" and "raise_on_warnings".
[ticket:2515]

Parenthesis will be applied to a compound SQL expression as

2013-10-13T00:21:38+00:00

rendered in the column list of a CREATE INDEX statement.
[ticket:2742]

- Fixed bug in default compiler plus those of postgresql, mysql, and

2013-10-13T00:13:27+00:00

mssql to ensure that any literal SQL expression values are
rendered directly as literals, instead of as bound parameters,
within a CREATE INDEX statement. [ticket:2742]
- don't need expression_as_ddl(); literal_binds and include_table
take care of this functionality.

Conflicts:
	lib/sqlalchemy/sql/util.py

- put exact version string in the test

2013-09-29T21:25:34+00:00

- use match with a .* preceding instead of search

Merge pull request #26 from hackop/ticket_2819

2013-09-29T21:25:19+00:00

re.match to re.search