sqlalchemy-commits Mailing List for SQLAlchemy (Page 22)
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-05-18 16:26:44
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c124fa36d5af/ Changeset: c124fa36d5af Branch: master User: zzzeek Date: 2016-05-18 15:43:38+00:00 Summary: Support "blank" schema when MetaData.schema is set Previously, it was impossible to have a Table that has None for a schema name when the "schema" parameter on MetaData was set. A new symbol sqlalchemy.schema.BLANK_SCHEMA is added which indicates that the schema name should unconditionally be set to None. In particular, this value must be passed within cross-schema foreign key reflection, so that a Table which is in the "default" schema can be represented properly. Fixes: #3716 Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e Affected #: 9 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4b31736343f1/ Changeset: 4b31736343f1 Branch: rel_1_0 User: zzzeek Date: 2016-05-18 15:44:56+00:00 Summary: Support "blank" schema when MetaData.schema is set Previously, it was impossible to have a Table that has None for a schema name when the "schema" parameter on MetaData was set. A new symbol sqlalchemy.schema.BLANK_SCHEMA is added which indicates that the schema name should unconditionally be set to None. In particular, this value must be passed within cross-schema foreign key reflection, so that a Table which is in the "default" schema can be represented properly. Fixes: #3716 Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e (cherry picked from commit c124fa36d5af2c85c87c51d24e92387adffbe3d2) 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-05-18 15:09:46
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fb45433f1504/ Changeset: fb45433f1504 Branch: None User: zzzeek Date: 2016-05-18 15:08:29+00:00 Summary: - 1.0.13 release date Change-Id: I1873dc22c233b5c3585eb7a203bc2352c7cfdbef 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-05-16 20:48:26
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f500bfee855e/ Changeset: f500bfee855e Branch: rel_1_0 User: zzzeek Date: 2016-05-16 19:52:07+00:00 Summary: - 1.0.13 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-05-16 17:19:05
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/735a0c04015f/ Changeset: 735a0c04015f Branch: None User: jayvdb Date: 2016-05-16 14:16:29+00:00 Summary: Fix TypeError during cx_Oracle connection cx_Oracle connection parameters user, password and dsn must be either a string or NULL. When they are passed a Python None object, "TypeError: expecting string, unicode or buffer object" is raised. Fixes: #3705 Change-Id: I8da5d8a227ca12c9bf17a6127460e413841951fb Pull-request: https://github.com/zzzeek/sqlalchemy/pull/271 (cherry picked from commit a60328473f78d68b65cc376c21aa8f50df867d26) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/8ac8fecf3f34/ Changeset: 8ac8fecf3f34 Branch: rel_1_0 User: zzzeek Date: 2016-05-16 17:18:49+00:00 Summary: Merge "Fix TypeError during cx_Oracle connection" into rel_1_0 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-05-16 17:13:06
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a51ab916622d/ Changeset: a51ab916622d Branch: None User: zzzeek Date: 2016-05-16 14:32:07+00:00 Summary: Accommodate "callable" bound param in evaluator Fixed bug in "evaluate" strategy of :meth:`.Query.update` and :meth:`.Query.delete` which would fail to accommodate a bound parameter with a "callable" value, as which occurs when filtering by a many-to-one equality expression along a relationship. Change-Id: I47758d3f5d8b9ea1a07e23166780d5f3c32b17f1 Fixes: #3700 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d3cf79bf8796/ Changeset: d3cf79bf8796 Branch: master User: zzzeek Date: 2016-05-16 17:12:51+00:00 Summary: Merge "Accommodate "callable" bound param in evaluator" 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-05-16 17:12:50
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0470abadd237/ Changeset: 0470abadd237 Branch: rel_1_0 User: zzzeek Date: 2016-05-16 14:33:36+00:00 Summary: Accommodate "callable" bound param in evaluator Fixed bug in "evaluate" strategy of :meth:`.Query.update` and :meth:`.Query.delete` which would fail to accommodate a bound parameter with a "callable" value, as which occurs when filtering by a many-to-one equality expression along a relationship. Change-Id: I47758d3f5d8b9ea1a07e23166780d5f3c32b17f1 Fixes: #3700 (cherry picked from commit a51ab916622dd016ce51d6be0969112817cc42ad) 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-05-16 17:12:18
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9611ba3a9d7c/ Changeset: 9611ba3a9d7c Branch: None User: jayvdb Date: 2016-05-16 14:15:19+00:00 Summary: Fix TypeError during cx_Oracle connection cx_Oracle connection parameters user, password and dsn must be either a string or NULL. When they are passed a Python None object, "TypeError: expecting string, unicode or buffer object" is raised. Fixes: #3705 Change-Id: I8da5d8a227ca12c9bf17a6127460e413841951fb Pull-request: https://github.com/zzzeek/sqlalchemy/pull/271 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/88cd6e4706cc/ Changeset: 88cd6e4706cc Branch: master User: zzzeek Date: 2016-05-16 17:11:54+00:00 Summary: Merge "Fix TypeError during cx_Oracle connection" 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-05-16 14:27:18
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/1873d8107ac8/ Changeset: 1873d8107ac8 Branch: None User: zzzeek Date: 2016-05-16 14:26:08+00:00 Summary: Fix formatting on test_evaluator Change-Id: Idcd77a570b19f1b022a74d67fa8253d922dadc67 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8c8b1bd53c2f/ Changeset: 8c8b1bd53c2f Branch: rel_1_0 User: zzzeek Date: 2016-05-16 14:26:35+00:00 Summary: Fix formatting on test_evaluator Change-Id: Idcd77a570b19f1b022a74d67fa8253d922dadc67 (cherry picked from commit 1873d8107ac8cf4258440914d68f12332220e244) 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-05-14 01:59:45
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8ecad78ba347/ Changeset: 8ecad78ba347 Branch: master User: iurisilvio Date: 2016-05-14 01:23:17+00:00 Summary: Handle `SSL error: decryption failed or bad record mac` This is another psycopg2 error message representing an unusable connection. Fixes #3715 Change-Id: Ida6e212963e9c7336bf2944e7ef928619ac3a0e7 Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/85 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/06fd549df499/ Changeset: 06fd549df499 Branch: rel_1_0 User: iurisilvio Date: 2016-05-14 01:26:42+00:00 Summary: Handle `SSL error: decryption failed or bad record mac` This is another psycopg2 error message representing an unusable connection. Fixes #3715 Change-Id: Ida6e212963e9c7336bf2944e7ef928619ac3a0e7 (cherry picked from commit 8ecad78ba3473d97df8ed4f20f28ddf966ce0277) Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/85 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-05-13 15:43:27
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ba3d4aa5baeb/ Changeset: ba3d4aa5baeb Branch: None User: Mark Sandan Date: 2016-05-07 01:26:31+00:00 Summary: change "psotgresql" to 'postgresql' in decorator Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9e75d3ed8fa5/ Changeset: 9e75d3ed8fa5 Branch: None User: zzzeek Date: 2016-05-13 15:41:51+00:00 Summary: Merge remote-tracking branch 'origin/pr/272' Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/1959263338d9/ Changeset: 1959263338d9 Branch: rel_1_0 User: Mark Sandan Date: 2016-05-13 15:42:18+00:00 Summary: change "psotgresql" to 'postgresql' in decorator (cherry picked from commit ba3d4aa5baebacfef8a56de66a5c06cd1372e893) 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-05-12 18:22:31
|
6 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2774113dab7d/ Changeset: 2774113dab7d Branch: None User: Frank Carnovale Date: 2016-05-12 16:57:11+00:00 Summary: typo in glossary#instrumentation: s/behviors/behaviors/ Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/1d81219aec83/ Changeset: 1d81219aec83 Branch: None User: Frank Carnovale Date: 2016-05-12 16:57:11+00:00 Summary: typo in glossary#FROMclause: s/incicates/indicates/ Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/fb289799f459/ Changeset: fb289799f459 Branch: None User: Frank Carnovale Date: 2016-05-12 16:57:11+00:00 Summary: typo in glossary#release: s/proces/process/ Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f5b314571284/ Changeset: f5b314571284 Branch: None User: Frank Carnovale Date: 2016-05-12 18:21:37+00:00 Summary: typo in glossary#instrumentation: s/behviors/behaviors/ (cherry picked from commit 2774113dab7d20ebe8879fdc6efaebf72ea9f770) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/b4f8b6f0e99d/ Changeset: b4f8b6f0e99d Branch: None User: Frank Carnovale Date: 2016-05-12 18:21:39+00:00 Summary: typo in glossary#FROMclause: s/incicates/indicates/ (cherry picked from commit 1d81219aec83317208cc85333256499636b19cf8) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f800daf387fb/ Changeset: f800daf387fb Branch: rel_1_0 User: Frank Carnovale Date: 2016-05-12 18:21:42+00:00 Summary: typo in glossary#release: s/proces/process/ (cherry picked from commit fb289799f4595b70c2dfc8620a10967c981ff4b0) 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-05-12 11:57:20
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c55ad9691900/ Changeset: c55ad9691900 Branch: rel_1_0 User: zzzeek Date: 2016-05-12 11:56:40+00:00 Summary: Add close_with_result to pessimistic connection example For connectionless execution, the recipe here will fail unless the should_close_with_result flag is temporarily set to False. Change-Id: Ib77b4439e8361b24478108c413b1ba720a68350f Fixes: #3712 (cherry picked from commit 7f08d8c93af1b574d1cc11af38baf26d9d59058f) 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-05-12 11:56:35
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7f08d8c93af1/ Changeset: 7f08d8c93af1 Branch: None User: zzzeek Date: 2016-05-12 11:54:14+00:00 Summary: Add close_with_result to pessimistic connection example For connectionless execution, the recipe here will fail unless the should_close_with_result flag is temporarily set to False. Change-Id: Ib77b4439e8361b24478108c413b1ba720a68350f Fixes: #3712 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-05-10 19:51:24
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0604116814a8/ Changeset: 0604116814a8 Branch: master User: zzzeek Date: 2016-05-10 16:55:23+00:00 Summary: Fix label referencing in SQL Server OFFSET logic Fixed bug where by ROW_NUMBER OVER clause applied for OFFSET selects in SQL Server would inappropriately substitute a plain column from the local statement that overlaps with a label name used by the ORDER BY criteria of the statement. Change-Id: Ic2500c886cbfc83a1ad5a2681783f008b9f23838 Fixes: #3711 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/40b0e4b424c8/ Changeset: 40b0e4b424c8 Branch: rel_1_0 User: zzzeek Date: 2016-05-10 16:57:08+00:00 Summary: Fix label referencing in SQL Server OFFSET logic Fixed bug where by ROW_NUMBER OVER clause applied for OFFSET selects in SQL Server would inappropriately substitute a plain column from the local statement that overlaps with a label name used by the ORDER BY criteria of the statement. Change-Id: Ic2500c886cbfc83a1ad5a2681783f008b9f23838 Fixes: #3711 (cherry picked from commit a4be7c92393e08607dc46f318e97803519052a93) 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-05-10 15:49:58
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/743e9d458994/ Changeset: 743e9d458994 Branch: master User: zzzeek Date: 2016-05-10 15:05:30+00:00 Summary: Check for duplicate calls to register_attribute_impl Fixed bug whereby the event listeners used for backrefs could be inadvertently applied multiple times, when using a deep class inheritance hierarchy in conjunction with mutiple mapper configuration steps. Change-Id: I712beaf4674e2323bf5b282922658020a6d00b53 Fixes: #3710 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a9f74400b179/ Changeset: a9f74400b179 Branch: rel_1_0 User: zzzeek Date: 2016-05-10 15:06:53+00:00 Summary: Check for duplicate calls to register_attribute_impl Fixed bug whereby the event listeners used for backrefs could be inadvertently applied multiple times, when using a deep class inheritance hierarchy in conjunction with mutiple mapper configuration steps. Change-Id: I712beaf4674e2323bf5b282922658020a6d00b53 Fixes: #3710 (cherry picked from commit 743e9d4589946f1a29cdec7f2f1a2e4ec0853db7) 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-05-05 21:10:24
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9bdd6f2b1f6b/ Changeset: 9bdd6f2b1f6b Branch: None User: zzzeek Date: 2016-05-05 21:07:40+00:00 Summary: Repair _orm_columns() to accommodate text() Fixed bug whereby passing a :func:`.text` construct to the :meth:`.Query.group_by` method would raise an error, instead of intepreting the object as a SQL fragment. Change-Id: I5fc2f590b76508d52e23b5fa9cf037ddea8080c3 fixes: #3706 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/eb0685e40f75/ Changeset: eb0685e40f75 Branch: rel_1_0 User: zzzeek Date: 2016-05-05 21:08:31+00:00 Summary: Repair _orm_columns() to accommodate text() Fixed bug whereby passing a :func:`.text` construct to the :meth:`.Query.group_by` method would raise an error, instead of intepreting the object as a SQL fragment. Change-Id: I5fc2f590b76508d52e23b5fa9cf037ddea8080c3 fixes: #3706 (cherry picked from commit 9bdd6f2b1f6b34a82b77849ec05811aa0279931d) 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-04-27 20:10:30
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/83a9e6e1fac2/ Changeset: 83a9e6e1fac2 Branch: rel_1_0 User: zzzeek Date: 2016-04-27 20:08:31+00:00 Summary: Fix pymssql sample URL A slash is required before building out the query string portion. Change-Id: Ie97fd3d07047d78e17cbaffed4ff54960a2b956e Fixes: #3696 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9a3c9ba7beb1/ Changeset: 9a3c9ba7beb1 Branch: None User: zzzeek Date: 2016-04-27 20:09:39+00:00 Summary: Fix pymssql sample URL A slash is required before building out the query string portion. Change-Id: Ie97fd3d07047d78e17cbaffed4ff54960a2b956e Fixes: #3696 (cherry picked from commit 83a9e6e1fac276090e60136aa4e9234ae23bc25a) 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-04-27 19:03:44
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8aa7369125f8/ Changeset: 8aa7369125f8 Branch: None User: jfinkels Date: 2016-04-27 06:35:55+00:00 Summary: Adds parentheses around prints in documentation This makes the docstring example code compatible with both Python 2 and Python 3. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9e77f40a313b/ Changeset: 9e77f40a313b Branch: None User: zzzeek Date: 2016-04-27 19:02:09+00:00 Summary: Merge remote-tracking branch 'origin/pr/263' 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-04-27 19:03:42
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c1adaea7cd2c/ Changeset: c1adaea7cd2c Branch: rel_1_0 User: jfinkels Date: 2016-04-27 19:03:06+00:00 Summary: Adds parentheses around prints in documentation This makes the docstring example code compatible with both Python 2 and Python 3. (cherry picked from commit 8aa7369125f831a74c9f024ce5dde73ecf812e63) 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-04-27 19:00:24
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f3bc60bdd809/ Changeset: f3bc60bdd809 Branch: master User: zzzeek Date: 2016-04-27 16:37:58+00:00 Summary: Don't double-process ResultMetaData for BufferedColumnResultProxy Fixed a bug in the result proxy used mainly by Oracle when binary and other LOB types are in play, such that when query / statement caching were used, the type-level result processors, notably that required by the binary type itself but also any other processor, would become lost after the first run of the statement due to it being removed from the cached result metadata. Change-Id: I751940866cffb4f48de46edc8137482eab59790c Fixes: #3699 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c2505259531d/ Changeset: c2505259531d Branch: rel_1_0 User: zzzeek Date: 2016-04-27 16:47:07+00:00 Summary: Don't double-process ResultMetaData for BufferedColumnResultProxy Fixed a bug in the result proxy used mainly by Oracle when binary and other LOB types are in play, such that when query / statement caching were used, the type-level result processors, notably that required by the binary type itself but also any other processor, would become lost after the first run of the statement due to it being removed from the cached result metadata. Change-Id: I751940866cffb4f48de46edc8137482eab59790c Fixes: #3699 (cherry picked from commit f3bc60bdd809235cbeb3f414717ac0e273269cf9) 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-04-27 00:02:18
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c3de4061fd49/ Changeset: c3de4061fd49 Branch: rel_1_0 User: zzzeek Date: 2016-04-27 00:00:43+00:00 Summary: Simplify directed graph example Changed the "directed graph" example to no longer consider integer identifiers of nodes as significant; the "higher" / "lower" references now allow mutual edges in both directions. Change-Id: Ibfd5b420f0451a6fc746f0bcbbbb062f8f88dc1d Fixes: #3698 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/84ba09a7d7b0/ Changeset: 84ba09a7d7b0 Branch: None User: zzzeek Date: 2016-04-27 00:01:22+00:00 Summary: Simplify directed graph example Changed the "directed graph" example to no longer consider integer identifiers of nodes as significant; the "higher" / "lower" references now allow mutual edges in both directions. Change-Id: Ibfd5b420f0451a6fc746f0bcbbbb062f8f88dc1d Fixes: #3698 (cherry picked from commit c3de4061fd490adcd8b75c79685f4a831b869f9e) 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-04-24 18:47:06
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0a0a9da999e2/ Changeset: 0a0a9da999e2 Branch: rel_1_0 User: zzzeek Date: 2016-04-24 18:46:27+00:00 Summary: - don't use --dropfirst when we are using ad-hoc DBs. dropfirst is unnecessary and causes collisions against other CI runs Change-Id: I47e9bc98cd6ef4ab90be25bae45897dabae16308 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-04-24 18:46:08
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ffb6fbf825d0/ Changeset: ffb6fbf825d0 Branch: None User: zzzeek Date: 2016-04-24 18:44:04+00:00 Summary: - don't use --dropfirst when we are using ad-hoc DBs. dropfirst is unnecessary and causes collisions against other CI runs Change-Id: I47e9bc98cd6ef4ab90be25bae45897dabae16308 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-04-21 16:22:51
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3db48cc62704/ Changeset: 3db48cc62704 Branch: rel_1_0 User: zzzeek Date: 2016-04-21 14:39:14+00:00 Summary: Fix result set handling for case insensitive dupe cols Fixed bug where when using ``case_sensitive=False`` with an :class:`.Engine`, the result set would fail to correctly accomodate for duplicate column names in the result set, causing an error when the statement is executed in 1.0, and preventing the "ambiguous column" exception from functioning in 1.1. Change-Id: If582bb9fdd057e4da3ae42f7180b17d1a1a2d98e Fixes: #3690 (cherry picked from commit 1f3e5d9826fe989f2212745f6b3592b2ef9b5e32) 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-04-21 16:22:36
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/1f3e5d9826fe/ Changeset: 1f3e5d9826fe Branch: master User: zzzeek Date: 2016-04-21 14:36:19+00:00 Summary: Fix result set handling for case insensitive dupe cols Fixed bug where when using ``case_sensitive=False`` with an :class:`.Engine`, the result set would fail to correctly accomodate for duplicate column names in the result set, causing an error when the statement is executed in 1.0, and preventing the "ambiguous column" exception from functioning in 1.1. Change-Id: If582bb9fdd057e4da3ae42f7180b17d1a1a2d98e Fixes: #3690 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. |
737 messages has been excluded from this view by a project administrator.
