summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Added documentation. Changed my mind - added get_foreign_table_names() only ↵pr/128Rodrigo Menezes2014-09-056-41/+26
| | | | to PGInspect and not in the Dialect. Added tests for PGInspect and removed a bunch of the old test scaffolding.
* Added get_foreign_table_names to interface and put it in the test requirements.Rodrigo Menezes2014-09-054-2/+19
|
* Fixing some pep8s and adding get_foreign_tables.Rodrigo Menezes2014-09-034-9/+38
|
* Removed changes that are no longer necessary for postgresql_relkind. Also, ↵Rodrigo Menezes2014-08-262-3/+5
| | | | removed newline changes.
* Merge branch 'master' of https://github.com/zzzeek/sqlalchemy into ↵Rodrigo Menezes2014-08-2649-2013/+2538
|\ | | | | | | feature/postgres-relkind
| * - changelog for pr bitbucket:28Mike Bayer2014-08-251-0/+9
| |
| * Merge branch 'mutable-dict-update' of ↵Mike Bayer2014-08-252-0/+16
| |\ | | | | | | | | | https://bitbucket.org/goodscloud/sqlalchemy into pr27
| | * add update() support to MutableDictMatt Chisholm2014-08-092-0/+16
| | |
| * | - changelog for pr bitbucket:27Mike Bayer2014-08-251-0/+10
| | |
| * | Merge branch 'mutable-dict-coerce-fix' of ↵Mike Bayer2014-08-252-3/+56
| |\ \ | | | | | | | | | | | | https://bitbucket.org/goodscloud/sqlalchemy into pr27
| | * | fix MutableDict.coerceMatt Chisholm2014-08-092-3/+56
| | |/ | | | | | | | | | 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.
| * | - mention that FOUND_ROWS is hardcoded; fixes #3146Mike Bayer2014-08-251-7/+5
| | |
| * | - The "resurrect" ORM event has been removed. This event hook hadMike Bayer2014-08-253-23/+8
| | | | | | | | | | | | | | | | | | no purpose since the old "mutable attribute" system was removed in 0.8. fixes #3171
| * | Merge branch 'pr129'Mike Bayer2014-08-233-1/+168
| |\ \ | | | | | | | | | | | | | | | | Conflicts: doc/build/changelog/changelog_10.rst
| | * | - pep8 formatting for pg table opts feature, testsMike Bayer2014-08-233-46/+145
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - add support for PG INHERITS - fix mis-named tests - changelog fixes #2051
| | * | Adding postgres create table options documentationpr/129Malik Diarra2014-08-171-0/+16
| | | |
| | * | Correcting options name from withoids to with_oidsMalik Diarra2014-08-172-6/+6
| | | |
| | * | quoting tablespace name in create table command in postgresql dialectMalik Diarra2014-08-172-1/+7
| | | |
| | * | Adding oids and on_commit table optionsMalik Diarra2014-08-172-1/+33
| | | |
| | * | Adding a tablespace options for postgresql create tableMalik Diarra2014-08-172-1/+15
| | | |
| * | | Merge remote-tracking branch 'origin/pr/131'Mike Bayer2014-08-211-1/+4
| |\ \ \
| | * | | Add note on begin_nested requiring rollback/commitpr/131Gunnlaugur Þór Briem2014-08-211-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | Merge pull request #130 from gthb/docfix-1mike bayer2014-08-213-4/+4
| |\ \ \ \ | | |/ / / | |/| | | Fix doc typos and copy-paste error
| | * | | Fix doc typo 'conjunection'pr/130Gunnlaugur Þór Briem2014-08-212-2/+2
| | | | |
| | * | | Fix copy-paste error in Delete docGunnlaugur Þór Briem2014-08-211-2/+2
| |/ / /
| * | | - fix linkMike Bayer2014-08-211-1/+1
| | | |
| * | | - The INSERT...FROM SELECT construct now implies ``inline=True``Mike Bayer2014-08-205-16/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | - pep8Mike Bayer2014-08-201-16/+29
| | | |
| * | | - factor out determination of current version id out ofMike Bayer2014-08-201-55/+55
| | | | | | | | | | | | | | | | _collect_update_commands and _collect_delete_commands
| * | | - Fixed bug in connection pool logging where the "connection checked out"Mike Bayer2014-08-203-12/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | - pep8 cleanupMike Bayer2014-08-202-25/+13
| | | |
| * | | - simplify PK logic in update for row switchMike Bayer2014-08-192-16/+9
| | | |
| * | | - optimize collection of cols we insert as noneMike Bayer2014-08-182-17/+11
| | | |
| * | | - move out checks for table in mapper._pks_by_tableMike Bayer2014-08-181-16/+32
| | | |
| * | | - further reorganize collect_insert_commands to distinguish betweenMike Bayer2014-08-181-13/+21
| | | | | | | | | | | | | | | | | | | | setting up given values vs. defaults. again trying to shoot for making this of more general use
| * | | - organize persistence methods in terms of generators,Mike Bayer2014-08-181-93/+94
| | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | - major simplification of _collect_update_commands. in particular,Mike Bayer2014-08-184-88/+77
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | - Fixed bug where attribute "set" events or columns withMike Bayer2014-08-175-20/+83
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``@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
| * | | - oldest screwup in the book, forgot the fileMike Bayer2014-08-161-0/+167
| |/ /
| * | - rework profiling, zoomark tests into single tests so thatMike Bayer2014-08-166-927/+408
| | | | | | | | | | | | they can be used under xdist
| * | - changelog for pullreq github:125Mike Bayer2014-08-162-0/+20
| | | | | | | | | | | | - add pg8000 version detection for the "sane multi rowcount" feature
| * | Merge remote-tracking branch 'origin/pr/125' into pr125Mike Bayer2014-08-164-75/+57
| |\ \
| | * | pg8000 now supports sane_multi_rowcountpr/125Tony Locke2014-08-021-1/+1
| | | | | | | | | | | | | | | | | | | | From pg8000-1.9.14 sane_multi_rowcount is supported so this commit updates the dialect accordingly.
| | * | two_phase_recover, COMMIT PREPARED in transactionTony Locke2014-08-022-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | Remove spurious print statements in pg8000 dialectTony Locke2014-08-021-2/+0
| | | |
| | * | PEP8 tidy of test/engine/test_reconnectTony Locke2014-08-021-58/+52
| | | |
| | * | With pg8000-1.9.13 passes engine/test_reconnectTony Locke2014-08-021-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | - support dialects w/o sane multi row count againMike Bayer2014-08-161-15/+33
| | | |
| * | | - need list() here for py3kMike Bayer2014-08-161-1/+4
| | | |
| * | | - max failures 25Mike Bayer2014-08-162-1/+4
| | | | | | | | | | | | | | | | - guard against some potential pytest snarkiness