delta/python-packages/sqlalchemy.git/lib/sqlalchemy/engine, branch pr/21

find some more inline imports and move them out

2013-08-04T19:28:40+00:00

- don't need resolve, don't need import for this. just look in sys.modules,

2013-08-04T19:03:50+00:00

since we are dealing with cycles in any case.

a missing cursor.close() here caused a huge amount of weird locking issues with pypy,

2013-08-02T17:27:30+00:00

what is strange is how it only occurred in some very specific places under very
particular conditions, perhaps it has to do with whether or not this cursor gets
gc'ed or not.

- assorted fixes raised by pypy 2.1beta2, but all of which are good

2013-08-02T00:25:56+00:00

ideas in general:
  - pypy2.1 w/ sqlite3 is the first DBAPI we're seeing returning
    unicode in cursor.description without being py3k.  add a new on-connect
    check for this, if we get back a u"", just don't do description decoding,
    should be OK for now.
  - the set tests in test_collection were assuming the two sets would be ordered
    the same when it tested pop(), can't really assume that.
  - test_serializer gets worse and worse, pickle is just not really viable here,
    ding out pypy
  - pypy2.1b2 seems to allow cursor.lastrowid to work (or we changed something?)
  - pool._threadconns.current() is a weakref, it can be None
  - another one of those logging.handlers imports

Dialect.initialize() is not called a second time if an :class:`.Engine`

2013-07-11T19:15:09+00:00

is recreated, due to a disconnect error.   This fixes a particular
issue in the Oracle 8 dialect, but in general the dialect.initialize()
phase should only be once per dialect.  Also in 0.8.3. [ticket:2776]

- refactor pool a bit so that intent between ConnectionRecord/ConnectionFairy is clear;

2013-07-02T17:14:21+00:00

make sure that the DBAPI connection passed to the reset-on-return events/dialect hooks
is also a "fairy", so that dictionaries like "info" are available.  [ticket:2770]
- rework the execution_options system so that the dialect is given the job of making
any immediate adjustments based on a set event.  move the "isolation level" logic to use
this new system.   Also work things out so that even engine-level execution options
can be used for things like isolation level; the dialect attaches a connect-event
handler in this case to handle the task.
- to support this new system as well as further extensibiltiy of execution options
add events engine_connect(), set_connection_execution_options(), set_engine_execution_options()

these notes about **kw are incorrect, we are talking about the return value here

2013-06-09T21:56:31+00:00

- get_unique_constraints() pull request

2013-06-09T21:54:11+00:00

- version (0.9 for now)
- changelog
- move the test into the test suite so that all dialects can take advantage of it

Add basic support of unique constraints reflection

2013-06-09T20:49:55+00:00

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.

Merge branch 'ticket_2587'

2013-06-05T01:38:56+00:00

Conflicts:
	test/profiles.txt
	test/sql/test_selectable.py