[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2014-08-21 00:19:11
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/89ff6df7dcdf/ Changeset: 89ff6df7dcdf Branch: None User: zzzeek Date: 2014-08-21 01:12:32 Summary: - pep8 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/71ca494f5186/ Changeset: 71ca494f5186 Branch: None User: zzzeek Date: 2014-08-21 02:14:20 Summary: - The INSERT...FROM SELECT construct now implies ``inline=True`` 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 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d3dea559e180/ Changeset: d3dea559e180 Branch: rel_0_9 User: zzzeek Date: 2014-08-21 02:18:30 Summary: - upgrade the note about inline=True to a warning, and make it clear that this flag should really be set all the time. ref #3169 Affected #: 1 file Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |