| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This was causing issues with Alembic (https://bitbucket.org/zzzeek/alembic/issue/127/auto-generate-seems-to-miss-unsigned)
|
|\ |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
Conflicts:
lib/sqlalchemy/orm/mapper.py
|
| |
|
|
|
|
| |
- fix broken py2k/py3k isms
|
|
|
|
|
|
|
|
|
|
|
|
| |
of dbapi.Error (such as ``TypeError``, ``NotImplementedError``, etc.)
will propagate the exception unchanged. Previously,
the error handling specific to the ``connect()`` routine would both
inappropriately run the exception through the dialect's
:meth:`.Dialect.is_disconnect` routine as well as wrap it in
a :class:`sqlalchemy.exc.DBAPIError`. It is now propagated unchanged
in the same way as occurs within the execute process. [ticket:2881]
- add tests for this in test_parseconnect, but also add tests in test_execute
to ensure the execute() behavior as well
|
| |
|
|
|
|
|
|
|
|
| |
attempts when an existing connection attempt is blocking. Previously,
the production of new connections was serialized within the block
that monitored overflow; the overflow counter is now altered within
it's own critical section outside of the connection process itself.
[ticket:2880]
|
|
|
|
|
|
|
|
|
|
|
| |
connection to be available, such that for a connection pool
with no timeout specified, it will every half a second break out of
the wait to check for the so-called "abort" flag, which allows the
waiter to break out in case the whole connection pool was dumped;
normally the waiter should break out due to a notify_all() but it's
possible this notify_all() is missed in very slim cases.
This is an extension of logic first introduced in 0.8.0, and the
issue has only been observed occasionally in stress tests.
|
| |
|
| |
|
| |
|
|
|
|
| |
requirements etc., just like 0.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
assisting with alembic installations that have upgraded and are dealing with
PG index/unique constraint reflection.
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.
|
|
|
|
| |
"is disconnect" codes with cx_oracle. [ticket:2864]
|
|
|
|
|
|
|
|
| |
standalone gendered pronoun with a gender-neutral subject, but also
have replaced all occurences of "his/her", "his or her", etc. The docs have always
strived to account for both genders in any non-specific singular pronoun,
however recent controversy in the community suggests
that a zero-gendered-pronoun policy is probably best going forward.
|
|
|
|
|
|
|
| |
versionadded
Conflicts:
lib/sqlalchemy/ext/mutable.py
|
|\
| |
| | |
Fixed a syntax error in example code.
|
| | |
|
| |
| |
| |
| |
| | |
Conflicts:
test/engine/test_execute.py
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
when a pre-DBAPI :class:`.StatementError` were raised within
:meth:`.Connection.execute`, causing encoding errors for
non-ASCII statements. The stringification now remains within
Python unicode thus avoiding encoding errors. [ticket:2871]
Conflicts:
test/engine/test_execute.py
|
| |
| |
| |
| |
| | |
(e.g. for a ``CAST`` or similar) would incorrectly render ``None CHAR``
or similar. [ticket:2870]
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
correctly with table or column names that contain non-ASCII
characters. [ticket:2869]
Conflicts:
lib/sqlalchemy/ext/serializer.py
lib/sqlalchemy/sql/selectable.py
lib/sqlalchemy/testing/assertions.py
|
|/
|
|
| |
in 0.9 for [ticket:2868]
|
|
|
|
|
|
|
| |
- use thread.join() for waiters_handled test
Conflicts:
test/engine/test_pool.py
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
"naming columns distinctly" and "column_prefix" sections since this is often what ppl are looking for. [ticket:2856] is related.
|
|
|
|
|
|
| |
query being generated would produce a "columns being replaced"
warning for a statement with two same-named columns,
as the internal SELECT wouldn't have use_labels set.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
when using the pypostgresql adapter, which returns these values
as lists vs. psycopg2's return type of string.
[ticket:2855]
Conflicts:
doc/build/changelog/changelog_09.rst
lib/sqlalchemy/__init__.py
|