sqlalchemy-commits Mailing List for SQLAlchemy (Page 20)
Brought to you by:
zzzeek
Menu
▾
▴
sqlalchemy-commits — SVN commits logged to this list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
(74) |
Mar
(167) |
Apr
(127) |
May
(190) |
Jun
(119) |
Jul
(77) |
Aug
(82) |
Sep
(84) |
Oct
(153) |
Nov
(45) |
Dec
(54) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(109) |
Feb
(80) |
Mar
(110) |
Apr
(106) |
May
(92) |
Jun
(147) |
Jul
(288) |
Aug
(307) |
Sep
(108) |
Oct
(156) |
Nov
(147) |
Dec
(134) |
| 2008 |
Jan
(126) |
Feb
(91) |
Mar
(184) |
Apr
(208) |
May
(212) |
Jun
(54) |
Jul
(106) |
Aug
(80) |
Sep
(58) |
Oct
(80) |
Nov
(119) |
Dec
(220) |
| 2009 |
Jan
(202) |
Feb
(50) |
Mar
(70) |
Apr
(46) |
May
(80) |
Jun
(61) |
Jul
(146) |
Aug
(81) |
Sep
(71) |
Oct
(74) |
Nov
(66) |
Dec
(82) |
| 2010 |
Jan
(112) |
Feb
(169) |
Mar
(235) |
Apr
(77) |
May
(22) |
Jun
(31) |
Jul
(46) |
Aug
(46) |
Sep
(70) |
Oct
(36) |
Nov
(37) |
Dec
(79) |
| 2011 |
Jan
(46) |
Feb
(54) |
Mar
(65) |
Apr
(73) |
May
(31) |
Jun
(46) |
Jul
(40) |
Aug
(36) |
Sep
(44) |
Oct
(33) |
Nov
(19) |
Dec
(10) |
| 2012 |
Jan
(60) |
Feb
(37) |
Mar
(35) |
Apr
(28) |
May
(27) |
Jun
(50) |
Jul
(33) |
Aug
(88) |
Sep
(64) |
Oct
(74) |
Nov
(62) |
Dec
(41) |
| 2013 |
Jan
(30) |
Feb
(37) |
Mar
(39) |
Apr
(52) |
May
(40) |
Jun
(85) |
Jul
(74) |
Aug
(76) |
Sep
(26) |
Oct
(76) |
Nov
(63) |
Dec
(65) |
| 2014 |
Jan
(68) |
Feb
(82) |
Mar
(87) |
Apr
(24) |
May
(66) |
Jun
(34) |
Jul
(86) |
Aug
(75) |
Sep
(70) |
Oct
(41) |
Nov
(23) |
Dec
(53) |
| 2015 |
Jan
(40) |
Feb
(39) |
Mar
(69) |
Apr
(64) |
May
(40) |
Jun
(43) |
Jul
(20) |
Aug
(48) |
Sep
(38) |
Oct
(28) |
Nov
(34) |
Dec
(44) |
| 2016 |
Jan
(82) |
Feb
(49) |
Mar
(25) |
Apr
(21) |
May
(19) |
Jun
(46) |
Jul
(38) |
Aug
(21) |
Sep
(33) |
Oct
(44) |
Nov
(26) |
Dec
(10) |
| 2017 |
Jan
(52) |
Feb
(18) |
Mar
(61) |
Apr
(43) |
May
(57) |
Jun
(36) |
Jul
(37) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bitbucket <com...@bi...> - 2016-07-01 14:40:15
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f8781840aff5/ Changeset: f8781840aff5 Branch: None User: zzzeek Date: 2016-07-01 14:39:05+00:00 Summary: - revert the RTD reqs workaround, we are self-hosting now Change-Id: Ie11361147d497c6eb6418cdc850ed277dfbd1de4 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...> - 2016-06-29 23:14:01
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/39c18b53aa7e/ Changeset: 39c18b53aa7e Branch: rel_1_0 User: pieterproigia Date: 2016-06-29 21:24:53+00:00 Summary: Repair pickling for Properties object Fixed bug whereby the ``__getstate__`` / ``__setstate__`` methods for sqlalchemy.util.Properties were non-working due to the transition in the 1.0 series to ``__slots__``. The issue potentially impacted some third-party applications. Pull request courtesy Pieter Mulder. Fixes: #3728 Change-Id: I01ebd425bbfe145747fea2edd0d2d412c74fd84d Pull-request: https://github.com/zzzeek/sqlalchemy/pull/286 (cherry picked from commit cab57e9bab04fbdea44690c08dff379a29eaab32) 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...> - 2016-06-29 21:41:25
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fcfff7712817/ Changeset: fcfff7712817 Branch: None User: pieterproigia Date: 2016-06-29 21:21:31+00:00 Summary: Repair pickling for Properties object Fixed bug whereby the ``__getstate__`` / ``__setstate__`` methods for sqlalchemy.util.Properties were non-working due to the transition in the 1.0 series to ``__slots__``. The issue potentially impacted some third-party applications. Pull request courtesy Pieter Mulder. Fixes: #3728 Change-Id: I01ebd425bbfe145747fea2edd0d2d412c74fd84d Pull-request: https://github.com/zzzeek/sqlalchemy/pull/286 (cherry picked from commit cab57e9bab04fbdea44690c08dff379a29eaab32) Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/07e5b7cf5436/ Changeset: 07e5b7cf5436 Branch: master User: zzzeek Date: 2016-06-29 21:41:03+00:00 Summary: Merge "Repair pickling for Properties object" 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...> - 2016-06-29 21:23:07
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/acd8b1c107d5/ Changeset: acd8b1c107d5 Branch: None User: zzzeek Date: 2016-06-29 15:14:28+00:00 Summary: Ensure @compiles calls down to the original compilation scheme Made a slight behavioral change in the ``sqlalchemy.ext.compiler`` extension, whereby the existing compilation schemes for an established construct would be removed if that construct was itself didn't already have its own dedicated ``__visit_name__``. This was a rare occurrence in 1.0, however in 1.1 :class:`.postgresql.ARRAY` subclasses :class:`.sqltypes.ARRAY` and has this behavior. As a result, setting up a compilation handler for another dialect such as SQLite would render the main :class:`.postgresql.ARRAY` object no longer compilable. Fixes: #3732 Change-Id: If2c1ada4eeb09157885888e41f529173902f2b49 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...> - 2016-06-24 00:21:08
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7c74d702a963/ Changeset: 7c74d702a963 Branch: master User: zzzeek Date: 2016-06-23 23:58:43+00:00 Summary: Make boolean processors consistent between Py/C; coerce to 1/0 The processing performed by the :class:`.Boolean` datatype for backends that only feature integer types has been made consistent between the pure Python and C-extension versions, in that the C-extension version will accept any integer value from the database as a boolean, not just zero and one; additionally, non-boolean integer values being sent to the database are coerced to exactly zero or one, instead of being passed as the original integer value. Change-Id: I01e647547fd7047bd549dd70e1fa202c51e8328b Fixes: #3730 Affected #: 6 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...> - 2016-06-20 18:23:36
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/bf03d4332ae3/ Changeset: bf03d4332ae3 Branch: master User: zzzeek Date: 2016-06-20 16:52:31+00:00 Summary: Don't reorder PrimaryKeyConstraint columns if explicit Dialed back the "order the primary key columns per auto-increment" described in :ref:`change_mysql_3216` a bit, so that if the :class:`.PrimaryKeyConstraint` is explicitly defined, the order of columns is maintained exactly, allowing control of this behavior when necessary. Change-Id: I9e7902c57a96c15968a6abf53e319acf15680da0 Fixes: #3726 Affected #: 5 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...> - 2016-06-20 16:51:51
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/91a102222749/ Changeset: 91a102222749 Branch: master User: zzzeek Date: 2016-06-20 15:45:24+00:00 Summary: Disable Enum string validation by default Rolled back the validation rules a bit in :class:`.Enum` to allow unknown string values to pass through, unless the flag ``validate_string=True`` is passed to the Enum; any other kind of object is still of course rejected. While the immediate use is to allow comparisons to enums with LIKE, the fact that this use exists indicates there may be more unknown-string-comparsion use cases than we expected, which hints that perhaps there are some unknown string-INSERT cases too. Change-Id: I7d1d79b374a7d47966d410998f77cd19294ab7b0 Fixes: #3725 Affected #: 6 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...> - 2016-06-20 15:43:45
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4e811fd72e61/ Changeset: 4e811fd72e61 Branch: None User: zzzeek Date: 2016-06-20 15:42:53+00:00 Summary: - create space for 1.1.0b2 Change-Id: I8815a68dcf6e5d27f3f82b02f939f72d9a412337 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...> - 2016-06-18 13:39:15
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/13f9578082ae/ Changeset: 13f9578082ae Branch: None User: zzzeek Date: 2016-06-18 13:35:54+00:00 Summary: - update alembic link Change-Id: I5ac6ba8234873fdd19bee6c1decd311a9cb4d55e Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/80cf17bf6f53/ Changeset: 80cf17bf6f53 Branch: rel_1_0 User: zzzeek Date: 2016-06-18 13:36:41+00:00 Summary: - update alembic link Change-Id: I5ac6ba8234873fdd19bee6c1decd311a9cb4d55e (cherry picked from commit 13f9578082ae669734d65a38cb6058e21df88362) Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/38b70dcd4471/ Changeset: 38b70dcd4471 Branch: rel_0_9 User: zzzeek Date: 2016-06-18 13:38:28+00:00 Summary: - update alembic link Change-Id: I5ac6ba8234873fdd19bee6c1decd311a9cb4d55e (cherry picked from commit 13f9578082ae669734d65a38cb6058e21df88362) 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...> - 2016-06-18 13:32:14
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fe6b549184c6/ Changeset: fe6b549184c6 Branch: None User: zzzeek Date: 2016-06-18 13:31:11+00:00 Summary: - missing indexable.rst Change-Id: Ida3ca92b496a1e3ebd761c100201d3660460c2bf 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...> - 2016-06-16 20:06:24
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ec36df00af58/ Changeset: ec36df00af58 Branch: None User: zzzeek Date: 2016-06-16 20:01:00+00:00 Summary: - dont need this Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d59cf4eb3f98/ Changeset: d59cf4eb3f98 Branch: None User: zzzeek Date: 2016-06-16 20:01:03+00:00 Summary: 1.1.0b1 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...> - 2016-06-16 20:06:08
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0f581bcf2596/ Changeset: 0f581bcf2596 Branch: None User: zzzeek Date: 2016-06-16 19:02:10+00:00 Summary: 1.1.0b1 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...> - 2016-06-16 19:00:50
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d7b8b475f8a5/ Changeset: d7b8b475f8a5 Branch: None User: Mark Sandan Date: 2016-06-16 15:43:02+00:00 Summary: Add DDLCompiler.create_table_suffix() Allows custom dialects to add keywords after the CREATE TABLE section. Change-Id: I6fa66dfcf00ef95122f491a9115410df2746cf88 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/21f47e6f7ac0/ Changeset: 21f47e6f7ac0 Branch: master User: zzzeek Date: 2016-06-16 19:00:49+00:00 Summary: Merge "Add DDLCompiler.create_table_suffix()" 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...> - 2016-06-16 15:53:58
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/42078107f160/ Changeset: 42078107f160 Branch: None User: Mark Sandan Date: 2016-06-16 15:51:53+00:00 Summary: update pytest good practices link in PyTest class Change-Id: Ie96edd05e962663e9ddeeda85b24858caabd3bfd Pull-request: https://github.com/zzzeek/sqlalchemy/pull/262 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d8da8e4e7dd6/ Changeset: d8da8e4e7dd6 Branch: master User: zzzeek Date: 2016-06-16 15:53:18+00:00 Summary: Merge "update pytest good practices link in PyTest class" 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...> - 2016-06-15 22:17:27
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/345cc1e304f3/ Changeset: 345cc1e304f3 Branch: None User: zzzeek Date: 2016-06-15 22:10:46+00:00 Summary: - flake8 Change-Id: I74e369d1d71c98cb0af58dde80b7d535d17cbdf7 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/22ae6b4c9fbc/ Changeset: 22ae6b4c9fbc Branch: None User: zzzeek Date: 2016-06-15 22:11:01+00:00 Summary: - flake8 Change-Id: I74e369d1d71c98cb0af58dde80b7d535d17cbdf7 (cherry picked from commit 345cc1e304f3dc75bf5362e6c9f1975230a94753) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/e5bdf96bc0b1/ Changeset: e5bdf96bc0b1 Branch: None User: zzzeek Date: 2016-06-15 22:15:46+00:00 Summary: - dont use id() to test identity as these can be recycled Change-Id: Ie4cb4924909d55c5962f66e36cd5325e8e8f0538 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/e4491103b7f9/ Changeset: e4491103b7f9 Branch: rel_1_0 User: zzzeek Date: 2016-06-15 22:16:04+00:00 Summary: - dont use id() to test identity as these can be recycled Change-Id: Ie4cb4924909d55c5962f66e36cd5325e8e8f0538 (cherry picked from commit e5bdf96bc0b1503c4e4c8461748cd061f624e346) 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...> - 2016-06-15 19:17:00
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/51e4512abd25/ Changeset: 51e4512abd25 Branch: None User: zzzeek Date: 2016-06-15 18:36:24+00:00 Summary: Interpret lateral, alias as from clauses Also add doc members for Lateral. Change-Id: Ic801c296377ce84230139c6a43ecb3e93a852832 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/20f2f5b169d3/ Changeset: 20f2f5b169d3 Branch: None User: saarni Date: 2016-06-15 18:42:08+00:00 Summary: Add TABLESAMPLE clause support. The TABLESAMPLE clause allows randomly selecting an approximate percentage of rows from a table. At least DB2, Microsoft SQL Server and recent Postgresql support this standard clause. Fixes: #3718 Change-Id: I3fb8b9223e12a57100df30876b461884c58d72fa Pull-request: https://github.com/zzzeek/sqlalchemy/pull/277 Affected #: 9 files https://bitbucket.org/zzzeek/sqlalchemy/commits/ecca1f814e6a/ Changeset: ecca1f814e6a Branch: None User: zzzeek Date: 2016-06-15 19:16:57+00:00 Summary: Merge "Interpret lateral, alias as from clauses" Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/5c80400ec7c5/ Changeset: 5c80400ec7c5 Branch: master User: zzzeek Date: 2016-06-15 19:17:10+00:00 Summary: Merge "Add TABLESAMPLE clause support." 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...> - 2016-06-15 17:54:38
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0620a76b582c/ Changeset: 0620a76b582c Branch: None User: youknowone Date: 2016-06-15 17:05:21+00:00 Summary: Add `sqlalchemy.ext.index` for indexed attributes for ORM Add `sqlalchemy.ext.index.index_property` which subscribe an index of a column with `Indexable` type. Co-authored-by: Mike Bayer <mi...@zz...> Change-Id: I238c23131e4fded5dc7f7a25eb02e26008099d00 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/235 Affected #: 8 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...> - 2016-06-14 19:23:39
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4e9ab7a72f0a/ Changeset: 4e9ab7a72f0a Branch: None User: Robin Thomas Date: 2016-06-14 19:03:14+00:00 Summary: Add ON CONFLICT support for Postgresql Fixes: #3529 Co-authored-by: Mike Bayer <mi...@zz...> Change-Id: Ie3bf6ad70d9be9f0e44938830e922db03573991a Pull-request: https://github.com/zzzeek/sqlalchemy/pull/258 Affected #: 10 files https://bitbucket.org/zzzeek/sqlalchemy/commits/cfb59ecc9bbd/ Changeset: cfb59ecc9bbd Branch: master User: zzzeek Date: 2016-06-14 19:23:17+00:00 Summary: Merge "Add ON CONFLICT support for Postgresql" Affected #: 10 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...> - 2016-06-14 17:29:29
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e7ea2a4e198f/ Changeset: e7ea2a4e198f Branch: rel_1_0 User: zzzeek Date: 2016-06-13 19:37:46+00:00 Summary: Deprecate FromClause.count() (pending for 1.1) count() here is misleading in that it not only counts from an arbitrary column in the table, it also does not make accommodations for DISTINCT, JOIN, etc. as the ORM-level function does. Core should not be attempting to provide a function like this. Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2 Fixes: #3724 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/f38f89084970/ Changeset: f38f89084970 Branch: master User: zzzeek Date: 2016-06-14 15:48:04+00:00 Summary: Deprecate FromClause.count() count() here is misleading in that it not only counts from an arbitrary column in the table, it also does not make accommodations for DISTINCT, JOIN, etc. as the ORM-level function does. Core should not be attempting to provide a function like this. Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2 Fixes: #3724 Affected #: 21 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...> - 2016-06-10 22:29:48
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7189d0bc8259/ Changeset: 7189d0bc8259 Branch: master User: zzzeek Date: 2016-06-10 21:24:36+00:00 Summary: Ensure CTE internals are handled during clone The CTE construct was missing a _copy_internals() method which would handle CTE-specific structures including _cte_alias, _restates during a clone operation. Change-Id: I9aeac9cd24d8f7ae6b70e52650d61f7c96cb6d7e Fixes: #3722 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...> - 2016-06-10 22:28:22
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/33e2a0230e63/ Changeset: 33e2a0230e63 Branch: rel_1_0 User: zzzeek Date: 2016-06-10 21:27:06+00:00 Summary: Ensure CTE internals are handled during clone The CTE construct was missing a _copy_internals() method which would handle CTE-specific structures including _cte_alias, _restates during a clone operation. Change-Id: I9aeac9cd24d8f7ae6b70e52650d61f7c96cb6d7e Fixes: #3722 (cherry picked from commit 7189d0bc82598c2d6dcbb55b054837416db2ee7d) 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...> - 2016-06-08 21:13:07
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/31a0da32a8af/ Changeset: 31a0da32a8af Branch: master User: iurisilvio Date: 2016-06-08 18:41:05+00:00 Summary: Support `postgresql_concurrently` on index dropping. Also adds version detection so that DROP INDEX CONCURRENTLY only renders if the Postgresql version is 9.2 or higher; for CREATE INDEX CONCURRENTLY, version detection is added to allow the phrase to omit if the Postgresql version is less than 8.2. Co-authored-by: Mike Bayer <mi...@zz...> Change-Id: I597287e0ebbbe256c957a3579b58ace6848ab4f4 Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/84 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...> - 2016-06-08 17:21:23
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/824c8664ed18/ Changeset: 824c8664ed18 Branch: None User: xflr6 Date: 2016-06-06 22:57:10+00:00 Summary: Support normal /materialized views in PG separately Fixes: #3588 Change-Id: Ifbfcab67375f289ddb5c4522f4b803cb8b7c34de Pull-request: https://github.com/zzzeek/sqlalchemy/pull/250 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/24d29a63b6a3/ Changeset: 24d29a63b6a3 Branch: None User: zzzeek Date: 2016-06-08 17:21:12+00:00 Summary: Merge "Support normal /materialized views in PG separately" Affected #: 4 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...> - 2016-06-08 17:18:53
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c99fc44e170b/ Changeset: c99fc44e170b Branch: None User: zzzeek Date: 2016-06-08 16:57:21+00:00 Summary: Use the "committed" values when extracting many-to-one lazyload value The scalar object set() method calls upon the lazy loader to get at the "old" value of the attriute, however doesn't ensure that the "committed" value of the foreign key attributes is used. If the user has manipulated these attributes and they themselves have pending, non committed changes, we get the "new" value which these attributes would have set up if they were flushed. "old" vs "new" value is always about how the value has changed since the load, so we always have to use the DB-persisted values for everything when looking for "old". Change-Id: I82bdc40ad0cf033c3a98f3361776cf3161542cd6 Fixes: #3708 Affected #: 4 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...> - 2016-06-08 15:52:33
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3ebd1b30eb39/ Changeset: 3ebd1b30eb39 Branch: None User: Sergey Skopin Date: 2016-06-08 15:24:57+00:00 Summary: Add 'FOR NO KEY UPDATE' / 'FOR KEY SHARE' support for Postgresql Adds ``key_share=True`` for with_for_update(). Co-authored-by: Mike Bayer <mi...@zz...> Change-Id: I74e0c3fcbc023e1dc98a1fa0c7db67b4c3693a31 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/279 Affected #: 8 files https://bitbucket.org/zzzeek/sqlalchemy/commits/65b3f4aaa072/ Changeset: 65b3f4aaa072 Branch: None User: zzzeek Date: 2016-06-08 15:52:22+00:00 Summary: Merge "Add 'FOR NO KEY UPDATE' / 'FOR KEY SHARE' support for Postgresql" Affected #: 8 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. |
737 messages has been excluded from this view by a project administrator.
