| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
to PGInspect and not in the Dialect. Added tests for PGInspect and removed a bunch of the old test scaffolding.
|
| | |
|
| | |
|
| |
|
|
| |
removed newline changes.
|
| |\
| |
| |
| | |
feature/postgres-relkind
|
| | | |
|
| | |\
| | |
| | |
| | | |
https://bitbucket.org/goodscloud/sqlalchemy into pr27
|
| | | | |
|
| | | | |
|
| | |\ \
| | | |
| | | |
| | | | |
https://bitbucket.org/goodscloud/sqlalchemy into pr27
|
| | | |/
| | |
| | |
| | | |
If a class inherited from MutableDict (say, for instance, to add an update() method), coerce() would give back an instance of MutableDict instead of an instance of the derived class.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
no purpose since the old "mutable attribute" system was removed
in 0.8.
fixes #3171
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
doc/build/changelog/changelog_10.rst
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- add support for PG INHERITS
- fix mis-named tests
- changelog
fixes #2051
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |\ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Avoid confusion about rollback/commit "must be issued" after
``session.begin_nested()`` --- this might be taken to mean call must be
*added*, but that's only true if not using the return value as a context
manager.
|
| | |\ \ \ \
| | |/ / /
| |/| | | |
Fix doc typos and copy-paste error
|
| | | | | | |
|
| | |/ / / |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
on :class:`.Insert`. This helps to fix a bug where an
INSERT...FROM SELECT construct would inadvertently be compiled
as "implicit returning" on supporting backends, which would
cause breakage in the case of an INSERT that inserts zero rows
(as implicit returning expects a row), as well as arbitrary
return data in the case of an INSERT that inserts multiple
rows (e.g. only the first row of many).
A similar change is also applied to an INSERT..VALUES
with multiple parameter sets; implicit RETURNING will no longer emit
for this statement either. As both of these constructs deal
with varible numbers of rows, the
:attr:`.ResultProxy.inserted_primary_key` accessor does not
apply. Previously, there was a documentation note that one
may prefer ``inline=True`` with INSERT..FROM SELECT as some databases
don't support returning and therefore can't do "implicit" returning,
but there's no reason an INSERT...FROM SELECT needs implicit returning
in any case. Regular explicit :meth:`.Insert.returning` should
be used to return variable numbers of result rows if inserted
data is needed.
fixes #3169
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
_collect_update_commands and _collect_delete_commands
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
debug logging message would not emit if the logging were set up using
``logging.setLevel()``, rather than using the ``echo_pool`` flag.
Tests to assert this logging have been added. This is a
regression that was introduced in 0.9.0.
fixes #3168
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
setting up given values vs. defaults. again trying to shoot for
making this of more general use
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
narrow down argument lists and generator items for each function
down to just what each function needs. This will help for them
to be of more multipurpose use for bulk operations
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
we only call upon the history API fully for primary key columns.
We also now skip the whole step of looking at PK columns and using
any history at all if no net changes are detected on the object.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
``@validates`` would have events triggered within the flush process,
when those columns were the targets of a "fetch and populate"
operation, such as an autoincremented primary key, a Python side
default, or a server-side default "eagerly" fetched via RETURNING.
fixes #3167
|
| | |/ / |
|
| | | |
| | |
| | |
| | | |
they can be used under xdist
|
| | | |
| | |
| | |
| | | |
- add pg8000 version detection for the "sane multi rowcount" feature
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
From pg8000-1.9.14 sane_multi_rowcount is supported so this commit
updates the dialect accordingly.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In test/engine/test_transaction/test_two_phase_recover(), a COMMIT
PREPARED is issued while in a transaction. This causes an error, and
a prepared transaction is left hanging around which causes
the subsequent test to hang. I've altered the test to execute the
offending query with autocommit=true, then when it gets to the COMMIT
PRPARED it can go ahead.
There's another complication for pg8000 because its tpc_recover() method
started a transaction if one wasn't already in progress. I've decided
that this is incorrect behaviour and so from pg8000-1.9.13 this method
never starts or stops a transaction.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The pg8000 dialect checks the text of the exception to determine if the
connection is closed. I'd (recklessly!) changed the text of the
exception in a recent version of the pg8000 driver adding capitalization
and a full stop. I've changed it back now so all works.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
- guard against some potential pytest snarkiness
|