sqlalchemy-commits Mailing List for SQLAlchemy (Page 24)
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-03-21 15:00:50
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/07a4b6cbcda6/ Changeset: 07a4b6cbcda6 Branch: None User: zzzeek Date: 2016-03-21 14:57:40+00:00 Summary: - Fixed bug where the negation of an EXISTS expression would not be properly typed as boolean in the result, and also would fail to be anonymously aliased in a SELECT list as is the case with a non-negated EXISTS construct. fixes #3682 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/dfe49c7b7f0c/ Changeset: dfe49c7b7f0c Branch: rel_1_0 User: zzzeek Date: 2016-03-21 14:58:08+00:00 Summary: - Fixed bug where the negation of an EXISTS expression would not be properly typed as boolean in the result, and also would fail to be anonymously aliased in a SELECT list as is the case with a non-negated EXISTS construct. fixes #3682 (cherry picked from commit 07a4b6cbcda6e6ee6e67893c5a5d2fd01e5f125f) 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-03-17 01:02:28
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/732c613eeb89/ Changeset: 732c613eeb89 Branch: None User: Benjamin Dopplinger Date: 2016-03-16 03:30:04+00:00 Summary: Fix typo Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/e3ea0c8b961b/ Changeset: e3ea0c8b961b Branch: rel_1_0 User: Benjamin Dopplinger Date: 2016-03-17 01:01:57+00:00 Summary: Fix typo (cherry picked from commit 732c613eeb890e7b7cbd04750468dac584151a31) 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-03-15 22:02:01
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/edbb32649960/ Changeset: edbb32649960 Branch: None User: zzzeek Date: 2016-03-15 22:01:23+00:00 Summary: - ensure engine is restored even if we had a failure in cleanup for stray connection Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9c2515c80fb2/ Changeset: 9c2515c80fb2 Branch: rel_1_0 User: zzzeek Date: 2016-03-15 22:01:43+00:00 Summary: - ensure engine is restored even if we had a failure in cleanup for stray connection (cherry picked from commit edbb32649960db29761e765fc74c025e9999c7dd) 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-03-15 21:48:23
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4d147c3b169a/ Changeset: 4d147c3b169a Branch: None User: zzzeek Date: 2016-03-15 21:47:34+00:00 Summary: - Added basic isolation level support to the SQL Server dialects via :paramref:`.create_engine.isolation_level` and :paramref:`.Connection.execution_options.isolation_level` parameters. fixes #3534 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-03-15 21:22:36
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a87b3c210111/ Changeset: a87b3c210111 Branch: None User: Roman Podoliaka Date: 2015-02-24 17:50:54+00:00 Summary: Add 'native' autocommit support for mysql drivers Sometimes it might be useful to have 'native' autocommit support provided by a DB API driver rather than rely on SQLAlchemy autocommit emulation. Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/224b03f9c006/ Changeset: 224b03f9c006 Branch: None User: zzzeek Date: 2016-03-15 20:41:17+00:00 Summary: Merge branch 'master' into pr157 Affected #: 363 files https://bitbucket.org/zzzeek/sqlalchemy/commits/31f96c27a5fe/ Changeset: 31f96c27a5fe Branch: None User: zzzeek Date: 2016-03-15 21:17:21+00:00 Summary: - changelog and docs for #3332, fixes #3332 - make docs for isolation level more consistent between postgresql and mysql - move mysql autocommit tests Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/49eb39366a0c/ Changeset: 49eb39366a0c Branch: rel_1_0 User: zzzeek Date: 2016-03-15 21:21:05+00:00 Summary: - backport doc improvements from 31f96c27a5fea302358ba580313a2f742c12b83d re: isolation_level settings for postgresql, mysql Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4bac8ad16f64/ Changeset: 4bac8ad16f64 Branch: rel_0_9 User: zzzeek Date: 2016-03-15 21:21:54+00:00 Summary: - backport doc improvements from 31f96c27a5fea302358ba580313a2f742c12b83d re: isolation_level settings for postgresql, mysql (cherry picked from commit 49eb39366a0ca54ce973147802864fd7c359adb3) 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-03-15 15:17:14
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8bc370ed382a/ Changeset: 8bc370ed382a Branch: None User: zzzeek Date: 2016-03-15 15:16:21+00:00 Summary: - add notes for pyodbc limitations with rowcount fixes #3675 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4f010530de8d/ Changeset: 4f010530de8d Branch: rel_1_0 User: zzzeek Date: 2016-03-15 15:16:43+00:00 Summary: - add notes for pyodbc limitations with rowcount fixes #3675 (cherry picked from commit 8bc370ed382a45654101fa34bac4a2886ce089c3) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/e81857d8dd1e/ Changeset: e81857d8dd1e Branch: rel_0_9 User: zzzeek Date: 2016-03-15 15:16:48+00:00 Summary: - add notes for pyodbc limitations with rowcount fixes #3675 (cherry picked from commit 8bc370ed382a45654101fa34bac4a2886ce089c3) 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-03-14 21:57:39
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/af92f6763d72/ Changeset: af92f6763d72 Branch: None User: zzzeek Date: 2016-03-14 21:56:57+00:00 Summary: - Fixed bug where a newly inserted instance that is rolled back would still potentially cause persistence conflicts on the next transaction, because the instance would not be checked that it was expired. This fix will resolve a large class of cases that erronously cause the "New instance with identity X conflicts with persistent instance Y" error. fixes #3677 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-03-13 20:39:58
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/6e5e64e27ef2/ Changeset: 6e5e64e27ef2 Branch: None User: jfinkels Date: 2016-03-13 20:37:55+00:00 Summary: Adds documentation to Query.slice(). Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d7178007fca2/ Changeset: d7178007fca2 Branch: rel_1_0 User: jfinkels Date: 2016-03-13 20:39:36+00:00 Summary: Adds documentation to Query.slice(). (cherry picked from commit 6e5e64e27ef2c6a86c9aebdcefdf2cd726f1476a) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/ccd546aac690/ Changeset: ccd546aac690 Branch: rel_0_9 User: jfinkels Date: 2016-03-13 20:39:40+00:00 Summary: Adds documentation to Query.slice(). (cherry picked from commit 6e5e64e27ef2c6a86c9aebdcefdf2cd726f1476a) 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-03-09 14:48:32
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f61194cb865d/ Changeset: f61194cb865d Branch: None User: apopovych Date: 2016-03-09 07:56:30+00:00 Summary: Update cascades.rst Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/71f8a6027f4d/ Changeset: 71f8a6027f4d Branch: rel_1_0 User: apopovych Date: 2016-03-09 14:47:46+00:00 Summary: Update cascades.rst (cherry picked from commit f61194cb865db8b29cc65e47782bb72e54b14ada) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f84cc5000f62/ Changeset: f84cc5000f62 Branch: rel_0_9 User: apopovych Date: 2016-03-09 14:47:51+00:00 Summary: Update cascades.rst (cherry picked from commit f61194cb865db8b29cc65e47782bb72e54b14ada) 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-03-08 14:29:24
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/be7f8e0b8110/ Changeset: be7f8e0b8110 Branch: None User: zzzeek Date: 2016-03-08 14:28:44+00:00 Summary: - skip GC tests here when coverage is enabled, seems to interfere Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a7491feb6c21/ Changeset: a7491feb6c21 Branch: rel_1_0 User: zzzeek Date: 2016-03-08 14:29:07+00:00 Summary: - skip GC tests here when coverage is enabled, seems to interfere (cherry picked from commit be7f8e0b81106c21fa7956f0c27cf207375681c4) 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-03-03 15:51:00
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0e7904e730c3/ Changeset: 0e7904e730c3 Branch: None User: zzzeek Date: 2016-03-03 15:50:18+00:00 Summary: - not sure why MySQL DROP DBs fail but we can't just ignore the error like this Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8bc90c066b52/ Changeset: 8bc90c066b52 Branch: rel_1_0 User: zzzeek Date: 2016-03-03 15:50:38+00:00 Summary: - not sure why MySQL DROP DBs fail but we can't just ignore the error like this (cherry picked from commit 0e7904e730c3d2b0d3a394ad60010158ee29050c) 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-03-03 01:28:57
|
8 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/399f92cd116b/ Changeset: 399f92cd116b Branch: None User: Athena Yao Date: 2016-03-02 19:16:14+00:00 Summary: Raise exception when we have multiple values with an unknown column. Fixes #3666. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a1de176d23ee/ Changeset: a1de176d23ee Branch: None User: Athena Yao Date: 2016-03-02 19:43:09+00:00 Summary: Add test for inserting multiple values Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/3d83e1639e13/ Changeset: 3d83e1639e13 Branch: None User: zzzeek Date: 2016-03-03 01:13:42+00:00 Summary: - changelog for #3666, fixes #3666 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/6b7c207801d8/ Changeset: 6b7c207801d8 Branch: None User: zzzeek Date: 2016-03-03 01:24:49+00:00 Summary: - move out unconsumed names tests from test_compiler out to test_insert, test_update - establish consistent names between existing unconsumed names tests and new ones added per ref #3666 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/59677e82fb23/ Changeset: 59677e82fb23 Branch: None User: Athena Yao Date: 2016-03-03 01:25:50+00:00 Summary: Raise exception when we have multiple values with an unknown column. Fixes #3666. (cherry picked from commit 399f92cd116b747f742b919ac9a3e79eb0637e8a) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/dfde3b221108/ Changeset: dfde3b221108 Branch: None User: Athena Yao Date: 2016-03-03 01:25:59+00:00 Summary: Add test for inserting multiple values (cherry picked from commit a1de176d23ee03724ce269d143790686f862b400) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/78364b7037e2/ Changeset: 78364b7037e2 Branch: None User: zzzeek Date: 2016-03-03 01:26:09+00:00 Summary: - changelog for #3666, fixes #3666 (cherry picked from commit 3d83e1639e1325af67d2bba390bd7c40838380b9) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d2adf9411591/ Changeset: d2adf9411591 Branch: rel_1_0 User: zzzeek Date: 2016-03-03 01:26:14+00:00 Summary: - move out unconsumed names tests from test_compiler out to test_insert, test_update - establish consistent names between existing unconsumed names tests and new ones added per ref #3666 (cherry picked from commit 6b7c207801d826db872aeda02e7c7b531df68034) 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-02-26 16:28:32
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/785224a92f39/ Changeset: 785224a92f39 Branch: rel_1_0 User: zzzeek Date: 2016-02-26 16:27:12+00:00 Summary: - unfortunately calling upon "_label" here makes it unclear if we're trying to hit columns without names yet and such, to suit the bug right now just make it specific to FunctionElement Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8a20d277c52b/ Changeset: 8a20d277c52b Branch: None User: zzzeek Date: 2016-02-26 16:27:49+00:00 Summary: - unfortunately calling upon "_label" here makes it unclear if we're trying to hit columns without names yet and such, to suit the bug right now just make it specific to FunctionElement (cherry picked from commit 785224a92f39bd5bdd05bbc66f4dd79736abded5) 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-02-26 05:22:04
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0210695bd97e/ Changeset: 0210695bd97e Branch: None User: zzzeek Date: 2016-02-26 05:20:39+00:00 Summary: - Anonymous labeling is applied to a :attr:`.func` construct that is passed to :func:`.column_property`, so that if the same attribute is referred to as a column expression twice the names are de-duped, thus avoiding "ambiguous column" errors. Previously, the ``.label(None)`` would need to be applied in order for the name to be de-anonymized. fixes #3663 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/aac2cb5007ce/ Changeset: aac2cb5007ce Branch: rel_1_0 User: zzzeek Date: 2016-02-26 05:21:12+00:00 Summary: - Anonymous labeling is applied to a :attr:`.func` construct that is passed to :func:`.column_property`, so that if the same attribute is referred to as a column expression twice the names are de-duped, thus avoiding "ambiguous column" errors. Previously, the ``.label(None)`` would need to be applied in order for the name to be de-anonymized. fixes #3663 (cherry picked from commit 0210695bd97e76f58d8781b69337816501482fb0) 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-02-26 04:28:20
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f8914288f012/ Changeset: f8914288f012 Branch: None User: zzzeek Date: 2016-02-26 04:27:49+00:00 Summary: - An improvement to the workings of :meth:`.Query.correlate` such that when a "polymorphic" entity is used which represents a straight join of several tables, the statement will ensure that all the tables within the join are part of what's correlating. fixes #3662 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-02-22 03:49:54
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/aa9ce3f521f2/ Changeset: aa9ce3f521f2 Branch: rel_1_0 User: zzzeek Date: 2016-02-22 03:46:31+00:00 Summary: - additional adjustment to the fix made in 8ad968f33100baeb3b13c7e0b724b6b79ab4277f for ref #3657. The Oracle dialect makes more use of the "select_wraps_for" feature than SQL server because Oracle doesn't have "TOP" for a limit-only select, so tests are showing more happening here. In the case where the select() has some dupe columns, these are deduped from the .c collection so a positional match between the wrapper and original can't use .inner_columns, because these collections wont match. Using _columns_plus_names instead which is the deduped collection that determines the SELECT display, which definitely have to match up. Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/eff7b4f29d2a/ Changeset: eff7b4f29d2a Branch: None User: zzzeek Date: 2016-02-22 03:49:29+00:00 Summary: - additional adjustment to the fix made in 8ad968f33100baeb3b13c7e0b724b6b79ab4277f for ref #3657. The Oracle dialect makes more use of the "select_wraps_for" feature than SQL server because Oracle doesn't have "TOP" for a limit-only select, so tests are showing more happening here. In the case where the select() has some dupe columns, these are deduped from the .c collection so a positional match between the wrapper and original can't use .inner_columns, because these collections wont match. Using _columns_plus_names instead which is the deduped collection that determines the SELECT display, which definitely have to match up. (cherry picked from commit aa9ce3f521f254da9879ede011e520ec35b8270e) 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-02-22 01:53:40
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/01809bddff5b/ Changeset: 01809bddff5b Branch: None User: zzzeek Date: 2016-02-22 01:52:43+00:00 Summary: - Fixed bug in "to_list" conversion where a single bytes object would be turned into a list of individual characters. This would impact among other things using the :meth:`.Query.get` method on a primary key that's a bytes object. fixes #3660 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c87d0bff3ada/ Changeset: c87d0bff3ada Branch: rel_1_0 User: zzzeek Date: 2016-02-22 01:53:21+00:00 Summary: - Fixed bug in "to_list" conversion where a single bytes object would be turned into a list of individual characters. This would impact among other things using the :meth:`.Query.get` method on a primary key that's a bytes object. fixes #3660 (cherry picked from commit 01809bddff5b6e93010eb139aed54526c6e6c058) 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-02-21 01:44:31
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8ad968f33100/ Changeset: 8ad968f33100 Branch: None User: zzzeek Date: 2016-02-21 01:22:38+00:00 Summary: - reworked the way the "select_wraps_for" expression is handled within visit_select(); this attribute was added in the 1.0 series to accommodate the subquery wrapping behavior of SQL Server and Oracle while also working with positional column targeting and no longer relying upon "key fallback" in order to target columns in such a statement. The IBM DB2 third-party dialect also has this use case, but its implementation is using regular expressions to rewrite the textual SELECT only and does not make use of a "wrapped" select at this time. The logic no longer attempts to reconcile proxy set collections as this was not deterministic, and instead assumes that the select() and the wrapper select() match their columns postionally, at least for the column positions they have in common, so it is now very simple and safe. fixes #3657. - as a side effect of #3657 it was also revealed that the strategy of calling upon a ResultProxy._getter was not correctly calling into NoSuchColumnError when an expected column was not present, and instead returned None up to loading.instances() to produce NoneType failures; added a raiseerr argument to _getter() which is called when we aren't expecting None, fixes #3658. Affected #: 9 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a1c1ce7f769f/ Changeset: a1c1ce7f769f Branch: None User: zzzeek Date: 2016-02-21 01:30:49+00:00 Summary: - version bump Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/cf818984ab52/ Changeset: cf818984ab52 Branch: rel_1_0 User: zzzeek Date: 2016-02-21 01:30:58+00:00 Summary: - reworked the way the "select_wraps_for" expression is handled within visit_select(); this attribute was added in the 1.0 series to accommodate the subquery wrapping behavior of SQL Server and Oracle while also working with positional column targeting and no longer relying upon "key fallback" in order to target columns in such a statement. The IBM DB2 third-party dialect also has this use case, but its implementation is using regular expressions to rewrite the textual SELECT only and does not make use of a "wrapped" select at this time. The logic no longer attempts to reconcile proxy set collections as this was not deterministic, and instead assumes that the select() and the wrapper select() match their columns postionally, at least for the column positions they have in common, so it is now very simple and safe. fixes #3657. - as a side effect of #3657 it was also revealed that the strategy of calling upon a ResultProxy._getter was not correctly calling into NoSuchColumnError when an expected column was not present, and instead returned None up to loading.instances() to produce NoneType failures; added a raiseerr argument to _getter() which is called when we aren't expecting None, fixes #3658. (cherry picked from commit 8ad968f33100baeb3b13c7e0b724b6b79ab4277f) Affected #: 9 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6713817e1186/ Changeset: 6713817e1186 Branch: None User: zzzeek Date: 2016-02-21 01:43:36+00:00 Summary: - update the mssql autoincrement reflection test to accommodate the new behavior of the autoincrement flag as per ref #3216 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-02-20 04:52:50
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/60a9d2da25da/ Changeset: 60a9d2da25da Branch: None User: jeffwidman Date: 2016-02-19 17:59:47+00:00 Summary: Add release date for 1.0.12 to changelog 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-02-19 04:46:01
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/98459628a6c4/ Changeset: 98459628a6c4 Branch: pr238 User: zzzeek Date: 2016-02-19 04:45:21+00:00 Summary: - transfer func.__doc__ to expr.__doc__ for hybrid_method if doc not present 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-02-18 22:44:27
|
6 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/713e884bbf32/ Changeset: 713e884bbf32 Branch: None User: singingwolfboy Date: 2016-02-18 21:42:35+00:00 Summary: Proxy docstring along to hybrid_property and hybrid_method Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/51491f6c8f37/ Changeset: 51491f6c8f37 Branch: None User: singingwolfboy Date: 2016-02-18 21:42:35+00:00 Summary: Failing test for documenting @hybrid_property with .expression Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/683ec6c974aa/ Changeset: 683ec6c974aa Branch: None User: zzzeek Date: 2016-02-18 21:45:29+00:00 Summary: - add another layer of Comparator to wrap expressions Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6b19a63f990b/ Changeset: 6b19a63f990b Branch: None User: zzzeek Date: 2016-02-18 22:00:35+00:00 Summary: - additional test adjustments. need to review carefully the impact of these behavioral changes Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/16d507d94b81/ Changeset: 16d507d94b81 Branch: None User: zzzeek Date: 2016-02-18 22:39:39+00:00 Summary: - add a new test suite based on the Amount hybrid blog post; this reveals the need for more specifics on ExprComparator Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/ce3a4cf62ab3/ Changeset: ce3a4cf62ab3 Branch: pr238 User: zzzeek Date: 2016-02-18 22:41:54+00:00 Summary: - and re-adjust this test now that we only cover one level deep of __clause_element__().... 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-02-18 16:34:07
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c97aa6378903/ Changeset: c97aa6378903 Branch: None User: zzzeek Date: 2016-02-18 16:33:19+00:00 Summary: - further edit the unnest() example to suit PG's esoteric requirements exactly Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/bba2269922ef/ Changeset: bba2269922ef Branch: rel_1_0 User: zzzeek Date: 2016-02-18 16:33:41+00:00 Summary: - further edit the unnest() example to suit PG's esoteric requirements exactly (cherry picked from commit c97aa63789036fc145503f03123275253ae02d2c) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/313c1261a620/ Changeset: 313c1261a620 Branch: rel_0_9 User: zzzeek Date: 2016-02-18 16:33:46+00:00 Summary: - further edit the unnest() example to suit PG's esoteric requirements exactly (cherry picked from commit c97aa63789036fc145503f03123275253ae02d2c) 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-02-17 23:03:34
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/594a974ede97/ Changeset: 594a974ede97 Branch: None User: zzzeek Date: 2016-02-17 23:01:20+00:00 Summary: - Fixed bug which would cause an eagerly loaded many-to-one attribute to not be loaded, if the joined eager load were from a row where the same entity were present multiple times, some calling for the attribute to be eagerly loaded and others not. The logic here is revised to take in the attribute even though a different loader path has handled the parent entity already. fixes #3431 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-02-17 21:54:07
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2965da0a5d89/ Changeset: 2965da0a5d89 Branch: None User: zzzeek Date: 2016-02-17 21:53:01+00:00 Summary: - handle parameter sets that aren't correctly formed, so that for example an exception object made within a test suite can still repr (error seen in Keystone) 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-02-17 20:21:29
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/bf1d03a9e58a/ Changeset: bf1d03a9e58a Branch: None User: zzzeek Date: 2016-02-17 20:21:00+00:00 Summary: - do the trailing comma logic of tuple repr() exactly 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. |
737 messages has been excluded from this view by a project administrator.
