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

Changed pg8000 dialect to cope with native JSON

2015-01-03T16:59:17+00:00

For versions > 1.10.1 pg8000 returns de-serialized JSON objects rather
than a string. SQL parameters are still strings though.

Make pg8000 version detection more robust

2014-12-16T21:03:04+00:00

pg8000 uses Versioneer, which means that development versions have
version strings that don't fit into the dotted triple number format.
Released versions will always fit the triple format though.

pg8000 client_encoding in create_engine()

2014-12-16T20:55:55+00:00

The pg8000 dialect now supports the setting of the PostgreSQL parameter
client_encoding from create_engine().

- The :meth:`.PGDialect.has_table` method will now query against

2014-12-04T17:01:19+00:00

``pg_catalog.pg_table_is_visible(c.oid)``, rather than testing
for an exact schema match, when the schema name is None; this
so that the method will also illustrate that temporary tables
are present.  Note that this is a behavioral change, as Postgresql
allows a non-temporary table to silently overwrite an existing
temporary table of the same name, so this changes the behavior
of ``checkfirst`` in that unusual scenario.
fixes #3264

- in lieu of adding a new system of translating bound parameter names

2014-11-10T22:58:09+00:00

for psycopg2 and others, encourage users to take advantage of positional
styles by documenting "paramstyle".   A section is added to psycopg2
specifically as this is a pretty common spot for named parameters
that may be unusually named.  fixes #3246.

- clean up unicode docs and clarify that client_encoding

2014-10-07T18:06:46+00:00

at the engine level is not the same thing as at the connect args
level.

- use provide_metadata for new unique constraint / index tests

2014-10-04T23:06:35+00:00

- add a test for PG reflection of unique index without any unique
constraint
- for PG, don't include 'duplicates_constraint' in the entry
if the index does not actually mirror a constraint
- use a distinct method for unique constraint reflection within table
- catch unique constraint not implemented condition; this may
be within some dialects and also is expected to be supported by
Alembic tests
- migration + changelogs for #3184
- add individual doc notes as well to MySQL, Postgreql
fixes #3184

Merge branch 'reflect-unique-constraints' of https://bitbucket.org/jerdfelt/sqlalchemy into pr30

2014-10-04T21:47:53+00:00

- A revisit to this issue first patched in 0.9.5, apparently

2014-09-29T21:33:53+00:00

psycopg2's ``.closed`` accessor is not as reliable as we assumed,
so we have added an explicit check for the exception messages
"SSL SYSCALL error: Bad file descriptor" and
"SSL SYSCALL error: EOF detected" when detecting an
is-disconnect scenario.   We will continue to consult psycopg2's
connection.closed as a first check.
fixes #3021

Reflect unique constraints when reflecting a Table object

2014-09-17T20:19:50+00:00

Calls to reflect a table did not create any UniqueConstraint objects.
The reflection core made no calls to get_unique_constraints and as
a result, the sqlite dialect would never reflect any unique constraints.

MySQL transparently converts unique constraints into unique indexes, but
SQLAlchemy would reflect those as an Index object and as a
UniqueConstraint. The reflection core will now deduplicate the unique
constraints.

PostgreSQL would reflect unique constraints as an Index object and as
a UniqueConstraint object. The reflection core will now deduplicate
the unique indexes.