delta/python-packages/sqlalchemy.git/lib/sqlalchemy/connectors, branch rel_0_7

happy new year (see #2645)

2013-01-01T23:58:03+00:00

- [feature] Added "read_timeout" flag to MySQLdb

2012-10-10T17:15:16+00:00

    dialect.  [ticket:2554]

whitespace removal

2012-08-10T15:22:37+00:00

- sql

2012-04-01T23:42:54+00:00

  - [bug] Removed warning when Index is created
    with no columns; while this might not be what
    the user intended, it is a valid use case
    as an Index could be a placeholder for just an
    index of a certain name.

- mssql
  - [feature] Added interim create_engine flag
    supports_unicode_binds to PyODBC dialect,
    to force whether or not the dialect
    passes Python unicode literals to PyODBC
    or not.

happy new year

2012-01-04T20:38:26+00:00

- [bug] pyodbc-based dialects now parse the

2011-12-04T18:29:29+00:00

pyodbc accurately as far as observed
pyodbc strings, including such gems
as "py3-3.0.1-beta4" [ticket:2318]
- [bug] use new pyodbc version detection for
_need_decimal_fix option, [ticket:2318]

- Changes to attempt support of FreeTDS 0.91 with

2011-09-18T19:33:12+00:00

    Pyodbc.  This includes that string binds are sent as
    Python unicode objects when FreeTDS 0.91 is detected,
    and a CAST(? AS NVARCHAR) is used when we detect
    for a table.   However, I'd continue
    to characterize Pyodbc + FreeTDS 0.91 behavior as
    pretty crappy, there are still many queries such
    as used in reflection which cause a core dump on
    Linux, and it is not really usable at all
    on OSX, MemoryErrors abound and just plain broken
    unicode support.   [ticket:2273]

- Adjusted the pyodbc dialect such that bound

2011-06-07T02:24:07+00:00

    values are passed as bytes and not unicode
    if the "Easysoft" unix drivers are detected.
    This is the same behavior as occurs with
    FreeTDS.  Easysoft appears to segfault
    if Python unicodes are passed under
    certain circumstances.

- Unit tests pass 100% on MySQL installed

2011-06-02T23:52:26+00:00

on windows, after aggressive exclusion of a wide variety
of tests.   Not clear to what degree the failures are related to
version 5.5 vs. the usage of windows, in particular the ON UPDATE CASCADE
immediately crashes the server.   The features being tested here are all
edge cases not likely to be used in typical MySQL environments.
- Removed the "adjust casing" step that would
fail when reflecting a table on MySQL
on windows with a mixed case name.  After some
experimenting with a windows MySQL server, it's
been determined that this step wasn't really
helping the situation much; MySQL does not return
FK names with proper casing on non-windows
platforms either, and removing the step at
least allows the reflection to act more like
it does on other OSes.   A warning here
has been considered but its difficult to
determine under what conditions such a warning
can be raised, so punted on that for now -
added some docs instead. [ticket:2181]

- supports_sane_rowcount will be set to False
if using MySQLdb and the DBAPI doesn't provide
the constants.CLIENT module.

- add connection and cursor to is_disconnect(). We aren't using it yet,

2011-02-09T20:06:32+00:00

but we'd like to.   Most DBAPIs don't give us anything we can do with it.
Some research was done on psycopg2 and it still seems like they give us
no adequate method (tried connection.closed, cursor.closed, connection.status).
mxodbc claims their .closed attribute will work (but I am skeptical).
- remove beahvior in pool that auto-invalidated a connection when
the cursor failed to create.  That's not the pool's job.  we need the conn
for the error logic.  Can't get any tests to fail, curious why that
behavior was there, guess we'll find out (or not).
- add support for psycopg2 version detection.  even though we have
no use for it yet...
- adjust one of the reconnect tests to work with oracle's
horrendously slow connect speed