Thread: [Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets (Page 8)
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2015-04-01 23:42:35
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/01a1c3256aee/ Changeset: 01a1c3256aee Branch: rel_0_9 User: zzzeek Date: 2015-04-01 23:37:05+00:00 Summary: - :class:`.Query` doesn't support joins, subselects, or special FROM clauses when using the :meth:`.Query.update` or :meth:`.Query.delete` methods; instead of silently ignoring these fields if methods like :meth:`.Query.join` or :meth:`.Query.select_from` has been called, a warning is emitted. In 1.0.0b5 this will raise an error. Partial cherry pick from 5302bcebb8e18fdad7448ffb60d2a2017eab26c8. fixes #3349 - don't realy need _no_select_modifiers anymore Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/fe1922764151/ Changeset: fe1922764151 Branch: None User: zzzeek Date: 2015-04-01 23:37:43+00:00 Summary: - :class:`.Query` doesn't support joins, subselects, or special FROM clauses when using the :meth:`.Query.update` or :meth:`.Query.delete` methods; instead of silently ignoring these fields if methods like :meth:`.Query.join` or :meth:`.Query.select_from` has been called, an error is raised. In 0.9.10 this only emits a warning. fixes #3349 - don't needlessly call _compile_context() and build up a whole statement that we never need. Construct QueryContext as it's part of the event contract, but don't actually call upon mapper attributes; use more direct systems of determining the update or delete table. - don't realy need _no_select_modifiers anymore Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/2cae4f262b2f/ Changeset: 2cae4f262b2f Branch: None User: zzzeek Date: 2015-04-01 23:41:26+00:00 Summary: - use odict here for test determinism 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. |
From: Bitbucket <com...@bi...> - 2015-04-02 16:22:22
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/359f471a1203/ Changeset: 359f471a1203 Branch: None User: zzzeek Date: 2015-04-02 16:19:15+00:00 Summary: - Fixed bug where the state tracking within multiple, nested :meth:`.Session.begin_nested` operations would fail to propagate the "dirty" flag for an object that had been updated within the inner savepoint, such that if the enclosing savepoint were rolled back, the object would not be part of the state that was expired and therefore reverted to its database state. fixes #3352 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7c32b4c2a61e/ Changeset: 7c32b4c2a61e Branch: rel_0_9 User: zzzeek Date: 2015-04-02 16:21:00+00:00 Summary: - Fixed bug where the state tracking within multiple, nested :meth:`.Session.begin_nested` operations would fail to propagate the "dirty" flag for an object that had been updated within the inner savepoint, such that if the enclosing savepoint were rolled back, the object would not be part of the state that was expired and therefore reverted to its database state. fixes #3352 (cherry picked from commit 359f471a1203cafd5dc99b5b078ba7d788b67cec) Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/5e04995a82c0/ Changeset: 5e04995a82c0 Branch: None User: zzzeek Date: 2015-04-02 16:21:54+00:00 Summary: - update 0.9 changelog from rel_0_9 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. |
From: Bitbucket <com...@bi...> - 2015-04-08 14:55:25
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c75c6732b115/ Changeset: c75c6732b115 Branch: None User: Ramiro Morales Date: 2015-04-05 22:14:54+00:00 Summary: - pymssql has PEP249 Binary contructor since 2.1.1 See https://github.com/pymssql/pymssql/commit/e7fb15dd29090e1f1bb570842b53aea1ec32d8f0 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/6ee3d6ce8177/ Changeset: 6ee3d6ce8177 Branch: None User: zzzeek Date: 2015-04-08 14:53:11+00:00 Summary: Merge remote-tracking branch 'origin/pr/166' into pr166 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/3f930732f136/ Changeset: 3f930732f136 Branch: None User: zzzeek Date: 2015-04-08 14:54:32+00:00 Summary: - changelog for pr github:166 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. |
From: Bitbucket <com...@bi...> - 2015-04-23 16:14:26
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ce1ab2bef3e5/ Changeset: ce1ab2bef3e5 Branch: None User: effem-git Date: 2015-04-23 11:00:42+00:00 Summary: Update base.py Fix TypeError: Boolean value of this clause is not defined Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/167a45a442a2/ Changeset: 167a45a442a2 Branch: pr168 User: zzzeek Date: 2015-04-23 15:40:40+00:00 Summary: changelog for #3380, fixes #3380 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/dd4240e43b41/ Changeset: dd4240e43b41 Branch: None User: zzzeek Date: 2015-04-23 16:07:56+00:00 Summary: - Fixed support for "literal_binds" mode when using limit/offset with Firebird, so that the values are again rendered inline when this is selected. Related to :ticket:`3034`. fixes #3381 Affected #: 9 files 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. |
From: Bitbucket <com...@bi...> - 2015-04-28 14:12:23
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/da327d0349b2/ Changeset: da327d0349b2 Branch: None User: Ernest Walzel Date: 2015-04-28 11:27:00+00:00 Summary: Fix typo in 'Relationships API' docs exprssed -> expressed Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/0783cb9337ad/ Changeset: 0783cb9337ad Branch: None User: zzzeek Date: 2015-04-28 14:10:40+00:00 Summary: Merge pull request #170 from eronisko/fix_typo Fix typo in 'Relationships API' docs Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/e26ccb284452/ Changeset: e26ccb284452 Branch: rel_0_9 User: Ernest Walzel Date: 2015-04-28 14:11:50+00:00 Summary: Fix typo in 'Relationships API' docs exprssed -> expressed (cherry picked from commit da327d0349b2af88700808c8e0041eda4c57882f) 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. |
From: Bitbucket <com...@bi...> - 2015-04-30 22:01:25
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2d64bd39ea2c/ Changeset: 2d64bd39ea2c Branch: None User: zzzeek Date: 2015-04-30 21:43:49+00:00 Summary: - rework this so that creator can maintain the same API as before Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d26c18bd9dcb/ Changeset: d26c18bd9dcb Branch: ticket_3355 User: zzzeek Date: 2015-04-30 21:43:53+00:00 Summary: - new features will be in 1.0.3 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0e98795ff2c7/ Changeset: 0e98795ff2c7 Branch: None User: zzzeek Date: 2015-04-30 21:51:14+00:00 Summary: - New features added to support engine/pool plugins with advanced functionality. Added a new "soft invalidate" feature to the connection pool at the level of the checked out connection wrapper as well as the :class:`._ConnectionRecord`. This works similarly to a modern pool invalidation in that connections aren't actively closed, but are recycled only on next checkout; this is essentially a per-connection version of that feature. A new event :class:`.PoolEvents.soft_invalidate` is added to complement it. fixes #3379 - Added new flag :attr:`.ExceptionContext.invalidate_pool_on_disconnect`. Allows an error handler within :meth:`.ConnectionEvents.handle_error` to maintain a "disconnect" condition, but to handle calling invalidate on individual connections in a specific manner within the event. - Added new event :class:`.DialectEvents.do_connect`, which allows interception / replacement of when the :meth:`.Dialect.connect` hook is called to create a DBAPI connection. Also added dialect plugin hooks :meth:`.Dialect.get_dialect_cls` and :meth:`.Dialect.engine_created` which allow external plugins to add events to existing dialects using entry points. fixes #3355 Affected #: 9 files 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. |
From: Bitbucket <com...@bi...> - 2015-05-08 16:43:36
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/5c897d9c6a84/ Changeset: 5c897d9c6a84 Branch: None User: zzzeek Date: 2015-05-08 16:18:07+00:00 Summary: - start 1.0.5 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/eb1bb84fbc10/ Changeset: eb1bb84fbc10 Branch: None User: zzzeek Date: 2015-05-08 16:37:55+00:00 Summary: - Added official support for a CTE used by the SELECT present inside of :meth:`.Insert.from_select`. This behavior worked accidentally up until 0.9.9, when it no longer worked due to unrelated changes as part of :ticket:`3248`. Note that this is the rendering of the WITH clause after the INSERT, before the SELECT; the full functionality of CTEs rendered at the top level of INSERT, UPDATE, DELETE is a new feature targeted for a later release. fixes #3418 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/87c605e3dc8b/ Changeset: 87c605e3dc8b Branch: rel_0_9 User: zzzeek Date: 2015-05-08 16:42:36+00:00 Summary: - Added official support for a CTE used by the SELECT present inside of :meth:`.Insert.from_select`. This behavior worked accidentally up until 0.9.9, when it no longer worked due to unrelated changes as part of :ticket:`3248`. Note that this is the rendering of the WITH clause after the INSERT, before the SELECT; the full functionality of CTEs rendered at the top level of INSERT, UPDATE, DELETE is a new feature targeted for a later release. fixes #3418 (cherry picked from commit eb1bb84fbc10c801c7269a3d38c9e0235327857e) Affected #: 3 files 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. |
From: Bitbucket <com...@bi...> - 2015-05-21 00:20:27
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9434356da630/ Changeset: 9434356da630 Branch: None User: Pierre Rochard Date: 2015-05-17 21:28:56+00:00 Summary: Correcting typo in introspection Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/cd8f25aa1a83/ Changeset: cd8f25aa1a83 Branch: None User: zzzeek Date: 2015-05-21 00:19:22+00:00 Summary: Merge pull request #173 from PierreRochard/patch-1 Correcting typo in introspection Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/805f49f6ec79/ Changeset: 805f49f6ec79 Branch: rel_0_9 User: Pierre Rochard Date: 2015-05-21 00:20:07+00:00 Summary: Correcting typo in introspection (cherry picked from commit 9434356da63006b3bfbb7833bb62def4cda17189) 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. |
From: Bitbucket <com...@bi...> - 2015-05-21 19:39:28
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/164f2ad2f433/ Changeset: 164f2ad2f433 Branch: rel_1_0 User: zzzeek Date: 2015-05-21 17:43:37+00:00 Summary: flake8 some tests Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/321f39e3987d/ Changeset: 321f39e3987d Branch: rel_0_9 User: zzzeek Date: 2015-05-21 17:49:11+00:00 Summary: flake8 some tests (cherry picked from commit 164f2ad2f433b3d297df709d617a1fc421495921) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/525cc6fe0247/ Changeset: 525cc6fe0247 Branch: master User: zzzeek Date: 2015-05-21 18:21:01+00:00 Summary: - Fixed regression in the :mod:`sqlalchemy.ext.mutable` extension as a result of the bugfix for :ticket:`3167`, where attribute and validation events are no longer called within the flush process. The mutable extension was relying upon this behavior in the case where a column level Python-side default were responsible for generating the new value on INSERT or UPDATE, or when a value were fetched from the RETURNING clause for "eager defaults" mode. The new value would not be subject to any event when populated and the mutable extension could not establish proper coercion or history listening. A new event :meth:`.InstanceEvents.refresh_flush` is added which the mutable extension now makes use of for this use case. fixes #3427 - Added new event :meth:`.InstanceEvents.refresh_flush`, invoked when an INSERT or UPDATE level default value fetched via RETURNING or Python-side default is invoked within the flush process. This is to provide a hook that is no longer present as a result of :ticket:`3167`, where attribute and validation events are no longer called within the flush process. - Added a new semi-public method to :class:`.MutableBase` :meth:`.MutableBase._get_listen_keys`. Overriding this method is needed in the case where a :class:`.MutableBase` subclass needs events to propagate for attribute keys other than the key to which the mutable type is associated with, when intercepting the :meth:`.InstanceEvents.refresh` or :meth:`.InstanceEvents.refresh_flush` events. The current example of this is composites using :class:`.MutableComposite`. Affected #: 7 files 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. |
From: Bitbucket <com...@bi...> - 2015-05-30 00:52:59
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/19571e2f8f4b/ Changeset: 19571e2f8f4b Branch: None User: Allen, Timothy Date: 2015-05-28 18:25:56+00:00 Summary: Update to correct TDS version; FreeTDS only supports up to 7.3. 8.0 is not a valid version (Microsoft released the spec late). Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/0766c80b9c02/ Changeset: 0766c80b9c02 Branch: None User: zzzeek Date: 2015-05-30 00:52:27+00:00 Summary: Merge remote-tracking branch 'origin/pr/176' Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f2b1f04e83d2/ Changeset: f2b1f04e83d2 Branch: rel_0_9 User: Allen, Timothy Date: 2015-05-30 00:52:43+00:00 Summary: Update to correct TDS version; FreeTDS only supports up to 7.3. 8.0 is not a valid version (Microsoft released the spec late). (cherry picked from commit 19571e2f8f4b621f3a1eaea198a8556497178015) 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. |
From: Bitbucket <com...@bi...> - 2015-06-14 00:43:49
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/09485d733131/ Changeset: 09485d733131 Branch: None User: Patrick Hayes Date: 2015-06-13 18:11:16+00:00 Summary: Fix primary key behaviour in bulk_update Suppose you have a model class with a primary key. Base = declarative_base() class User(Base): id = Column(BigInteger, primary_key=True) name = Column(String) Previously, running `bulk_update_mappings(User, {'id': 1, 'name': 'hello'})` would emit the following: ```UPDATE users SET id=1, name='hello' WHERE id=1``` This is contrary to the stated behaviour, where primary keys are omitted from the SET clause. Furthermore, this behaviour is harmful, as it can cause the db engine to lock over-aggresively (at least in Postgres). With this change, the emitted SQL is: ```UPDATE users SET name='hello' WHERE id=1``` Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/2497d559ddeb/ Changeset: 2497d559ddeb Branch: None User: zzzeek Date: 2015-06-14 00:15:17+00:00 Summary: - add changelog for #3451, with 09485d733131b667813f44eb0b6807b698668ee7 fixes #3451 - also add a bulk_insert_mappings test Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/bcbfcca2360a/ Changeset: bcbfcca2360a Branch: None User: zzzeek Date: 2015-06-14 00:27:06+00:00 Summary: - restore the approach we have for pk_params, but in order to suit #3451 exclude these columns from the "params" dictionary in the first place, revises pr github:181 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. |
From: Bitbucket <com...@bi...> - 2015-06-26 18:46:00
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/5717186122d5/ Changeset: 5717186122d5 Branch: None User: Yuri Baida Date: 2015-06-26 17:45:48+00:00 Summary: Fix code examples in automap's documentation Fix camelize_classname and pluralize_collection functions as they didn't work as expected. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/012b3bd0b2a0/ Changeset: 012b3bd0b2a0 Branch: None User: zzzeek Date: 2015-06-26 18:44:56+00:00 Summary: Merge pull request #185 from megabyde/master Fix code examples in automap's documentation Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/3a432462a5c7/ Changeset: 3a432462a5c7 Branch: rel_0_9 User: Yuri Baida Date: 2015-06-26 18:45:41+00:00 Summary: Fix code examples in automap's documentation Fix camelize_classname and pluralize_collection functions as they didn't work as expected. (cherry picked from commit 5717186122d5538e53205268846beb7143a3d4cc) 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. |
From: Bitbucket <com...@bi...> - 2015-07-23 01:12:16
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9140a2f6af17/ Changeset: 9140a2f6af17 Branch: None User: zzzeek Date: 2015-07-22 23:59:09+00:00 Summary: - categorize this correctly Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8c494c855aa0/ Changeset: 8c494c855aa0 Branch: rel_0_9 User: zzzeek Date: 2015-07-22 23:59:26+00:00 Summary: - categorize this correctly Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/552f1f135f66/ Changeset: 552f1f135f66 Branch: None User: zzzeek Date: 2015-07-23 00:00:13+00:00 Summary: 1.0.8 Affected #: 2 files 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. |
From: Bitbucket <com...@bi...> - 2015-07-29 21:41:40
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d8efa2257ec6/ Changeset: d8efa2257ec6 Branch: None User: zzzeek Date: 2015-07-29 21:40:47+00:00 Summary: - Fixed support for cx_Oracle version 5.2, which was tripping up SQLAlchemy's version detection under Python 3 and inadvertently not using the correct unicode mode for Python 3. This would cause issues such as bound variables mis-interpreted as NULL and rows silently not being returned. fixes #3491 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/bd0f65400ed2/ Changeset: bd0f65400ed2 Branch: rel_1_0 User: zzzeek Date: 2015-07-29 21:41:18+00:00 Summary: - Fixed support for cx_Oracle version 5.2, which was tripping up SQLAlchemy's version detection under Python 3 and inadvertently not using the correct unicode mode for Python 3. This would cause issues such as bound variables mis-interpreted as NULL and rows silently not being returned. fixes #3491 (cherry picked from commit d8efa2257ec650b345ec6e840984387263a957a6) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/fd6c64609cbf/ Changeset: fd6c64609cbf Branch: rel_0_9 User: zzzeek Date: 2015-07-29 21:41:22+00:00 Summary: - Fixed support for cx_Oracle version 5.2, which was tripping up SQLAlchemy's version detection under Python 3 and inadvertently not using the correct unicode mode for Python 3. This would cause issues such as bound variables mis-interpreted as NULL and rows silently not being returned. fixes #3491 (cherry picked from commit d8efa2257ec650b345ec6e840984387263a957a6) Affected #: 2 files 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. |
From: Bitbucket <com...@bi...> - 2015-08-14 19:35:29
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b00b430e8751/ Changeset: b00b430e8751 Branch: None User: zzzeek Date: 2015-08-14 19:34:01+00:00 Summary: - add tests for InstanceEvents.init, InstanceEvents.init_failure - ensure that kwargs can be modified in-place within InstanceEvents.init and that these take effect for the __init__ method. - improve documentation for these and related events, including that kwargs can be modified in-place. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/42281066ca82/ Changeset: 42281066ca82 Branch: rel_1_0 User: zzzeek Date: 2015-08-14 19:34:57+00:00 Summary: - add tests for InstanceEvents.init, InstanceEvents.init_failure - ensure that kwargs can be modified in-place within InstanceEvents.init and that these take effect for the __init__ method. - improve documentation for these and related events, including that kwargs can be modified in-place. (cherry picked from commit b00b430e87512d721ad30c81fdcb35a5253dfc0a) Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4377f345c6c7/ Changeset: 4377f345c6c7 Branch: rel_0_9 User: zzzeek Date: 2015-08-14 19:35:02+00:00 Summary: - add tests for InstanceEvents.init, InstanceEvents.init_failure - ensure that kwargs can be modified in-place within InstanceEvents.init and that these take effect for the __init__ method. - improve documentation for these and related events, including that kwargs can be modified in-place. (cherry picked from commit b00b430e87512d721ad30c81fdcb35a5253dfc0a) Affected #: 3 files 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. |
From: Bitbucket <com...@bi...> - 2015-08-21 20:37:44
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e0a8030048f4/ Changeset: e0a8030048f4 Branch: None User: zzzeek Date: 2015-08-21 20:36:15+00:00 Summary: - rework the "controlling DDL sequences" documentation to refer mostly to the DDL object; this system is primarily useful in that case, and not for built-in objects. Reference that the built-in case is not really viable right now. References #3442. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/2759ec3e8a3a/ Changeset: 2759ec3e8a3a Branch: rel_1_0 User: zzzeek Date: 2015-08-21 20:37:17+00:00 Summary: - rework the "controlling DDL sequences" documentation to refer mostly to the DDL object; this system is primarily useful in that case, and not for built-in objects. Reference that the built-in case is not really viable right now. References #3442. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f71596bdd576/ Changeset: f71596bdd576 Branch: rel_0_9 User: zzzeek Date: 2015-08-21 20:37:21+00:00 Summary: - rework the "controlling DDL sequences" documentation to refer mostly to the DDL object; this system is primarily useful in that case, and not for built-in objects. Reference that the built-in case is not really viable right now. References #3442. 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. |
From: Bitbucket <com...@bi...> - 2015-08-26 21:21:35
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/cfae9c2eaf00/ Changeset: cfae9c2eaf00 Branch: None User: zzzeek Date: 2015-08-26 19:15:55+00:00 Summary: - Added support for the SQL-standard function :class:`.array_agg`, which automatically returns an :class:`.Array` of the correct type and supports index / slice operations. As arrays are only supported on Postgresql at the moment, only actually works on Postgresql. fixes #3132 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7c4512cbeb1c/ Changeset: 7c4512cbeb1c Branch: None User: zzzeek Date: 2015-08-26 21:19:27+00:00 Summary: - Added support for "set-aggregate" functions of the form ``<function> WITHIN GROUP (ORDER BY <criteria>)``, using the method :class:`.FunctionElement.within_group`. A series of common set-aggregate functions with return types derived from the set have been added. This includes functions like :class:`.percentile_cont`, :class:`.dense_rank` and others. fixes #1370 - make sure we use func.name for all _literal_as_binds in functions.py so we get consistent naming behavior for parameters. Affected #: 12 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4d63b472f272/ Changeset: 4d63b472f272 Branch: None User: zzzeek Date: 2015-08-26 21:20:56+00:00 Summary: Merge branch 'ticket_3516' Affected #: 26 files 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. |
From: Bitbucket <com...@bi...> - 2015-08-27 19:57:42
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d459afa8dbf7/ Changeset: d459afa8dbf7 Branch: None User: zzzeek Date: 2015-08-27 19:56:00+00:00 Summary: - reword and update documentation on passive_updates=False; as virtually all DBs now support ON UPDATE CASCADE other than Oracle, there's no need to try to reimplement more functionality here and users should be encouraged to forego natural PKs unless their target platform supports them. references #2666 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7de0e558e154/ Changeset: 7de0e558e154 Branch: rel_1_0 User: zzzeek Date: 2015-08-27 19:57:16+00:00 Summary: - reword and update documentation on passive_updates=False; as virtually all DBs now support ON UPDATE CASCADE other than Oracle, there's no need to try to reimplement more functionality here and users should be encouraged to forego natural PKs unless their target platform supports them. references #2666 (cherry picked from commit d459afa8dbf73b8d9d620d09dede97e3461b6b3f) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/794181697aef/ Changeset: 794181697aef Branch: rel_0_9 User: zzzeek Date: 2015-08-27 19:57:21+00:00 Summary: - reword and update documentation on passive_updates=False; as virtually all DBs now support ON UPDATE CASCADE other than Oracle, there's no need to try to reimplement more functionality here and users should be encouraged to forego natural PKs unless their target platform supports them. references #2666 (cherry picked from commit d459afa8dbf73b8d9d620d09dede97e3461b6b3f) Affected #: 2 files 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. |
From: Bitbucket <com...@bi...> - 2015-08-28 03:40:43
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/956907a4b15f/ Changeset: 956907a4b15f Branch: None User: zzzeek Date: 2015-08-28 03:38:14+00:00 Summary: - use consistent and descriptive language in all cases where we refer to the "weak_identity_map" option, and add additional exposition in the session documentation which refers to it. fixes #3517 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/fa1211eec934/ Changeset: fa1211eec934 Branch: rel_1_0 User: zzzeek Date: 2015-08-28 03:39:04+00:00 Summary: - use consistent and descriptive language in all cases where we refer to the "weak_identity_map" option, and add additional exposition in the session documentation which refers to it. fixes #3517 (cherry picked from commit 956907a4b15f6dcc492582a7ad03706ff62d96fb) Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6192af397f0f/ Changeset: 6192af397f0f Branch: rel_0_9 User: zzzeek Date: 2015-08-28 03:40:13+00:00 Summary: - use consistent and descriptive language in all cases where we refer to the "weak_identity_map" option, and add additional exposition in the session documentation which refers to it. fixes #3517 (cherry picked from commit 956907a4b15f6dcc492582a7ad03706ff62d96fb) Conflicts: lib/sqlalchemy/orm/identity.py Affected #: 3 files 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. |
From: Bitbucket <com...@bi...> - 2015-08-28 22:19:24
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4cfd05210c87/ Changeset: 4cfd05210c87 Branch: None User: zzzeek Date: 2015-08-28 20:25:35+00:00 Summary: - add new documentation that applies to all modern SQLA versions, detailing ORM event recipes across the board. Affected #: 8 files https://bitbucket.org/zzzeek/sqlalchemy/commits/44d5d4e201a7/ Changeset: 44d5d4e201a7 Branch: None User: zzzeek Date: 2015-08-28 21:43:46+00:00 Summary: - wip, add event signatures and test stubs Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d79102715d42/ Changeset: d79102715d42 Branch: ticket_2677 User: zzzeek Date: 2015-08-28 22:18:54+00:00 Summary: - wip Affected #: 2 files 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. |
From: Bitbucket <com...@bi...> - 2015-08-31 17:13:53
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/6d0c0994e9a0/ Changeset: 6d0c0994e9a0 Branch: None User: zzzeek Date: 2015-08-31 17:13:04+00:00 Summary: - add a note about DISTINCT in query w/ ORDER BY, references #3518 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/2d48b9de5ad5/ Changeset: 2d48b9de5ad5 Branch: rel_1_0 User: zzzeek Date: 2015-08-31 17:13:27+00:00 Summary: - add a note about DISTINCT in query w/ ORDER BY, references #3518 (cherry picked from commit 6d0c0994e9a08cf5d149af0314970d5f6e25b159) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/5c8d1f33cd10/ Changeset: 5c8d1f33cd10 Branch: rel_0_9 User: zzzeek Date: 2015-08-31 17:13:31+00:00 Summary: - add a note about DISTINCT in query w/ ORDER BY, references #3518 (cherry picked from commit 6d0c0994e9a08cf5d149af0314970d5f6e25b159) 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. |
From: Bitbucket <com...@bi...> - 2015-09-03 20:43:48
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/176ac6ab0915/ Changeset: 176ac6ab0915 Branch: None User: zzzeek Date: 2015-09-03 20:42:43+00:00 Summary: - update moved link, fixes #3351 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/6eb8901f6259/ Changeset: 6eb8901f6259 Branch: rel_1_0 User: zzzeek Date: 2015-09-03 20:43:22+00:00 Summary: - update moved link, fixes #3351 (cherry picked from commit 176ac6ab0915f99d378c7d9be67e9c0a73ab1800) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f47fcc83c88d/ Changeset: f47fcc83c88d Branch: rel_0_9 User: zzzeek Date: 2015-09-03 20:43:26+00:00 Summary: - update moved link, fixes #3351 (cherry picked from commit 176ac6ab0915f99d378c7d9be67e9c0a73ab1800) 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. |
From: Bitbucket <com...@bi...> - 2015-09-10 14:02:12
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/03797b78475b/ Changeset: 03797b78475b Branch: None User: zzzeek Date: 2015-09-10 14:00:46+00:00 Summary: - add a new FAQ recipe for "walk all objects", replacing the need to use mapper.cascade_iterator() for this purpose as it was not really designed for that use case. Add docs to cascade_iterator() pointing to the recipe. fixes #3498 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/517eba3896cd/ Changeset: 517eba3896cd Branch: rel_1_0 User: zzzeek Date: 2015-09-10 14:01:40+00:00 Summary: - add a new FAQ recipe for "walk all objects", replacing the need to use mapper.cascade_iterator() for this purpose as it was not really designed for that use case. Add docs to cascade_iterator() pointing to the recipe. fixes #3498 (cherry picked from commit 03797b78475bec9fb9c15f8e926414f3720a273c) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/86900687f13c/ Changeset: 86900687f13c Branch: rel_0_9 User: zzzeek Date: 2015-09-10 14:01:45+00:00 Summary: - add a new FAQ recipe for "walk all objects", replacing the need to use mapper.cascade_iterator() for this purpose as it was not really designed for that use case. Add docs to cascade_iterator() pointing to the recipe. fixes #3498 (cherry picked from commit 03797b78475bec9fb9c15f8e926414f3720a273c) Affected #: 2 files 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. |
From: Bitbucket <com...@bi...> - 2015-09-10 14:29:44
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ad28e228e30b/ Changeset: ad28e228e30b Branch: None User: zzzeek Date: 2015-09-10 14:28:42+00:00 Summary: - call it deque, since you can really pop from either side Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/dafab9bb0cae/ Changeset: dafab9bb0cae Branch: rel_1_0 User: zzzeek Date: 2015-09-10 14:29:15+00:00 Summary: - call it deque, since you can really pop from either side Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/6c5e781368c6/ Changeset: 6c5e781368c6 Branch: rel_0_9 User: zzzeek Date: 2015-09-10 14:29:19+00:00 Summary: - call it deque, since you can really pop from either side 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. |
From: Bitbucket <com...@bi...> - 2015-09-14 15:03:47
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fe41e39b9b77/ Changeset: fe41e39b9b77 Branch: None User: zzzeek Date: 2015-09-14 15:02:43+00:00 Summary: - add new entry for sharing of Engine across process boundaries Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/7369b51054ab/ Changeset: 7369b51054ab Branch: rel_1_0 User: zzzeek Date: 2015-09-14 15:03:02+00:00 Summary: - add new entry for sharing of Engine across process boundaries (cherry picked from commit fe41e39b9b776c18a03dde0540a45e1f0100d44b) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/718191e2ccec/ Changeset: 718191e2ccec Branch: rel_0_9 User: zzzeek Date: 2015-09-14 15:03:08+00:00 Summary: - add new entry for sharing of Engine across process boundaries (cherry picked from commit fe41e39b9b776c18a03dde0540a45e1f0100d44b) 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. |