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

Fix cross references

2013-11-17T22:37:55+00:00

- remove informix dialect, moved out to https://bitbucket.org/zzzeek/sqlalchemy_informixdb

2013-11-17T18:45:23+00:00

- remove informix, maxdb, access symbols from tests etc.

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

2013-10-27T22:14:44+00:00

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

- Fixed bug where Oracle table reflection using synonyms would fail

2013-10-25T23:11:53+00:00

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

- Fix and test parsing of MySQL foreign key options within reflection;

2013-10-25T21:18:40+00:00

this complements the work in :ticket:`2183` where we begin to support
reflection of foreign key options such as ON UPDATE/ON DELETE
cascade. [ticket:2839]

Merge branch 'master' of github.com:ijl/sqlalchemy into merge_2183

2013-10-25T21:01:38+00:00

- The typing system now handles the task of rendering "literal bind" values,

2013-10-20T20:59:56+00:00

e.g. values that are normally bound parameters but due to context must
be rendered as strings, typically within DDL constructs such as
CHECK constraints and indexes (note that "literal bind" values
become used by DDL as of :ticket:`2742`).  A new method
:meth:`.TypeEngine.literal_processor` serves as the base, and
:meth:`.TypeDecorator.process_literal_param` is added to allow wrapping
of a native literal rendering method. [ticket:2838]
- enhance _get_colparams so that we can send flags like literal_binds into
INSERT statements
- add support in PG for inspecting standard_conforming_strings
- add a new series of roundtrip tests based on INSERT of literal plus SELECT
for basic literal rendering in dialect suite

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

2013-10-18T23:34:58+00:00

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

2013-10-18T23:00:05+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-18T18:44:01+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]