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

Regression from this ticket caused the unsupported keyword

2013-05-15T19:46:29+00:00

"true" to render, added logic to convert this to 1/0
for SQL server.
[ticket:2682]

Updated mysqlconnector dialect to check for disconnect based

2013-04-29T23:49:28+00:00

on the apparent string message sent in the exception; tested
against mysqlconnector 1.0.9.

- fix long-outdated documentation for sql_mode/ansiquotes,

2013-04-29T23:21:44+00:00

closes [ticket:1552]

oracle doesn't have TRUE/FALSE, put 1/0 here, see how that goes

2013-04-26T23:49:48+00:00

need to test for (list, tuple) here and not hasattr("iter")

2013-04-26T23:48:43+00:00

since Py3K strings have __iter__

- only search in the exception before the first newline, to avoid

2013-04-23T17:07:36+00:00

false positives for SQL statements containing certain text

Opened up the checking for "disconnect" with psycopg2/libpq

2013-04-22T23:33:39+00:00

to check for all the various "disconnect" messages within
the full exception hierarchy.  Specifically the
"closed the connection unexpectedly" message has now been
seen in at least three different exception types.
[ticket:2712]

tweak this some more to handle the array being empty again

2013-04-22T21:24:31+00:00

- change to [ticket:2681], pre-coerce the array to list

2013-04-22T21:08:02+00:00

unconditonally instead so that it works in all cases.

The operators for the Postgresql ARRAY type supports

2013-04-22T20:57:15+00:00

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]