| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|\
| |
| | |
Makes gaerdbms for App Engine use local MySQL server when running in dev_appserver2
|
| | |
|
| | |
|
| |
| |
| |
| | |
dev_appserver2.
|
| |
| |
| |
| | |
- use an isinstance() check, concerned a TypeError might be indiscriminate
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, one can specify the prefix length for an index
column using 'mysql_length' keyword argument when creating
an Index instance. But in case of composite indexes the
prefix length value is applied only to the last column.
Extend the existing API in way so that 'mysql_length' argument
value can be either:
- an integer specifying the same prefix length value
for each column of an index
- a (column_name --> integer value) mapping specifying
the prefix length value for each column of an index
separately
Fixes issue #2704.
|
| |
|
|
|
|
|
|
|
| |
a CAST call that was added in 0.8.1 to help with driver issues,
which apparently is not compatible on 2000.
The CAST remains in place for SQL Server 2005 and greater.
[ticket:2747]
|
|\
| |
| |
| |
| |
| | |
Conflicts:
test/profiles.txt
test/sql/test_selectable.py
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
:class:`.ForeignKeyConstraint` will not render the ``DEFERRABLE`` keyword
on the MySQL dialect. For a long time we left this in place because
a non-deferrable foreign key would act very differently than a deferrable
one, but some environments just disable FKs on MySQL, so we'll be less
opinionated here. [ticket:2721]
|
| |
| |
| |
| |
| | |
- restore the rollback cleanup handler, pg8000 is mostly obsolete
as a dialect and the firebird drivers need it
|
|/
|
|
| |
not happening too well (I need to stick with linux + freetds 0.91, I know)
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
lib/sqlalchemy/dialects/postgresql/hstore.py
lib/sqlalchemy/util/__init__.py
lib/sqlalchemy/util/compat.py
|
| |
| |
| |
| | |
- fix test
|
| | |
|
| |
| |
| |
| |
| | |
add unicode encoding for py2k for the non-native hstore, pullreq for
native psycopg2 support coming....
|
| |
| |
| |
| |
| |
| |
| | |
to executemany(),
so just unconditionally turn this into a list
- this one test segfaults only on py3k + cx_oracle
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
probably be one in test_query or test_unicode...)
- fix up test_unitofwork
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
encoded in them vs. unicode escaping. not worth figuring out how to combine
these right now
|
| |\ \ |
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
- went through examples/ and cleaned out excess list() calls
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
- fix test
|
| | | | | |
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | | |
add unicode encoding for py2k for the non-native hstore, pullreq for
native psycopg2 support coming....
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
"true" to render, added logic to convert this to 1/0
for SQL server.
[ticket:2682]
|
| |/
|/|
| |
| |
| | |
on the apparent string message sent in the exception; tested
against mysqlconnector 1.0.9.
|
|/
|
|
| |
closes [ticket:1552]
|
| |
|
|
|
|
| |
since Py3K strings have __iter__
|
|
|
|
| |
false positives for SQL statements containing certain text
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
unconditonally instead so that it works in all cases.
|