Basic type support for the new range types in postgres 9.2
add support for range operators listed in http://www.postgresql.org/docs/9.2/interactive/functions-range.html
Implement EXCLUDE constraints for postgres.
Documentation for the new range type support.
- skip this test for py3k.   serializer kind of a bust
Add AUTOCOMMIT isolation level support for psycopg2

One can use this to emit statements, which can not be
executed within a transaction (e. g. CREATE DATABASE):

    from sqlalchemy import create_engine

    eng = create_engine('postgresql://test:test@localhost/test')

    conn = eng.connect().execution_options(isolation_level='AUTOCOMMIT')
    conn.execute('CREATE DATABASE test2;')

Fixes issue #2072.
don't create a history entry when an object in a backref has changed

The code that determines whether an object in a relation has been added/removed does not take into account that that relation may be a backref. If the relation is a backref, then nothing on the current table is changing, and therefore no history entry should be created.
Fixed bug in polymorphic SQL generation where multiple joined-inheritance
entities against the same base class joined to each other as well
would not track columns on the base table independently of each other if
the string of joins were more than two entities long.  Also in 0.8.2.
[ticket:2759]
Merge pull request #7 from malor/psycopg2_execution_options

Add AUTOCOMMIT isolation level support for psycopg2
- changelog
- docs
- clean up this test (really we don't even need this, it's not testing much)
- for the moment, put a catch in it to see if we can trap that issue
on jenkins
can remove this, issue is fixed
Merged in goodscloud/sqlalchemy (pull request #2)

don't create a history entry when an object in a backref has changed
Merge branch 'master' of bitbucket.org:zzzeek/sqlalchemy
changelog
changelog for 0.8
Forgot final check that a delete in a backref also doesn't create a new version

follow up to https://bitbucket.org/zzzeek/sqlalchemy/pull-request/2
migration for [ticket:2751]
- rework PropComparator.adapted() to be PropComparator.adapt_to_entity(),
passes in AliasedInsp and allows more flexibility.
- rework the AliasedClass/AliasedInsp relationship so that AliasedInsp has
all state and functionality.  AliasedClass is just a facade.
[ticket:2756]
turn this requirement back down as the simpler serialize works better now