sqlalchemy-commits Mailing List for SQLAlchemy (Page 62)
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...> - 2014-07-16 17:44:45
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a7ed17e71437/ Changeset: a7ed17e71437 Branch: rel_0_8 User: zzzeek Date: 2014-07-16 19:42:23 Summary: - backport #3093 to 0.8, fixes #3093 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/81f5631b4422/ Changeset: 81f5631b4422 Branch: rel_0_9 User: zzzeek Date: 2014-07-16 19:43:57 Summary: - forwards-port changelog for ref #3093 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/889013529feb/ Changeset: 889013529feb Branch: None User: zzzeek Date: 2014-07-16 19:44:27 Summary: - forwards-port changelog for ref #3093 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...> - 2014-07-16 14:53:00
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f024ce3b2940/ Changeset: f024ce3b2940 Branch: rel_0_8 User: zzzeek Date: 2014-07-16 16:52:35 Summary: - need Integer here as #1765 is in 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...> - 2014-07-15 23:00:22
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/828cf1263aee/ Changeset: 828cf1263aee Branch: None User: zzzeek Date: 2014-07-16 00:59:44 Summary: - use an odict here to ensure ordering of properties Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f0aa49268ac5/ Changeset: f0aa49268ac5 Branch: rel_0_9 User: zzzeek Date: 2014-07-16 01:00:04 Summary: - use an odict here to ensure ordering of properties 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...> - 2014-07-15 19:55:55
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/6575b5f98006/ Changeset: 6575b5f98006 Branch: rel_0_9 User: zzzeek Date: 2014-07-15 21:55:12 Summary: - add a full env for pypy, name it funny to avoid hidden/undocumented tox behavior Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/921d487e4115/ Changeset: 921d487e4115 Branch: None User: zzzeek Date: 2014-07-15 21:55:37 Summary: - add a full env for pypy, name it funny to avoid hidden/undocumented tox behavior 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...> - 2014-07-15 17:35:29
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e63767ed47ab/ Changeset: e63767ed47ab Branch: None User: zzzeek Date: 2014-07-15 19:34:55 Summary: - fully flake8 this file Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/77bf768eea63/ Changeset: 77bf768eea63 Branch: rel_0_9 User: zzzeek Date: 2014-07-15 19:35:14 Summary: - fully flake8 this file 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...> - 2014-07-15 17:22:43
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/61384fd0e529/ Changeset: 61384fd0e529 Branch: None User: zzzeek Date: 2014-07-15 19:20:55 Summary: - Fixed a regression caused by :ticket:`2976` released in 0.9.4 where the "outer join" propagation along a chain of joined eager loads would incorrectly convert an "inner join" along a sibling join path into an outer join as well, when only descendant paths should be receiving the "outer join" propagation; additionally, fixed related issue where "nested" join propagation would take place inappropriately between two sibling join paths. this is accomplished by re-introducing the removed flag "allow_innerjoin", now inverted and named "chained_from_outerjoin". Propagating this flag allows us to know when we have encountered an outerjoin along a load path, without confusing it for state obtained from a sibling path. fixes #3131 ref #2976 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/43663e7aac99/ Changeset: 43663e7aac99 Branch: rel_0_9 User: zzzeek Date: 2014-07-15 19:22:28 Summary: - Fixed a regression caused by :ticket:`2976` released in 0.9.4 where the "outer join" propagation along a chain of joined eager loads would incorrectly convert an "inner join" along a sibling join path into an outer join as well, when only descendant paths should be receiving the "outer join" propagation; additionally, fixed related issue where "nested" join propagation would take place inappropriately between two sibling join paths. this is accomplished by re-introducing the removed flag "allow_innerjoin", now inverted and named "chained_from_outerjoin". Propagating this flag allows us to know when we have encountered an outerjoin along a load path, without confusing it for state obtained from a sibling path. fixes #3131 ref #2976 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...> - 2014-07-15 16:26:24
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3d7b18863813/ Changeset: 3d7b18863813 Branch: None User: zzzeek Date: 2014-07-15 18:25:38 Summary: - Fixed a SQLite join rewriting issue where a subquery that is embedded as a scalar subquery such as within an IN would receive inappropriate substitutions from the enclosing query, if the same table were present inside the subquery as were in the enclosing query such as in a joined inheritance scenario. fixes #3130 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/b090e3a3e274/ Changeset: b090e3a3e274 Branch: rel_0_9 User: zzzeek Date: 2014-07-15 18:26:08 Summary: - Fixed a SQLite join rewriting issue where a subquery that is embedded as a scalar subquery such as within an IN would receive inappropriate substitutions from the enclosing query, if the same table were present inside the subquery as were in the enclosing query such as in a joined inheritance scenario. fixes #3130 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...> - 2014-07-15 02:45:18
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f4653729a6ff/ Changeset: f4653729a6ff Branch: None User: zzzeek Date: 2014-07-15 04:44:33 Summary: - wrestle with conv() and tests some more Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a904cd01d88a/ Changeset: a904cd01d88a Branch: rel_0_9 User: zzzeek Date: 2014-07-15 04:44:59 Summary: - wrestle with conv() and tests some more 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...> - 2014-07-15 01:12:11
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/03c736408800/ Changeset: 03c736408800 Branch: rel_0_9 User: zzzeek Date: 2014-07-15 03:11:16 Summary: - allow the compilation rule that gets the formatted name to again have the chance to veto rendering, as the naming convention can make the decision that the name is "none" or not now. Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/dbc8bbfba359/ Changeset: dbc8bbfba359 Branch: None User: zzzeek Date: 2014-07-15 03:11:51 Summary: - allow the compilation rule that gets the formatted name to again have the chance to veto rendering, as the naming convention can make the decision that the name is "none" or not now. 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...> - 2014-07-15 00:27:36
|
16 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/eb4abda81172/ Changeset: eb4abda81172 Branch: None User: zzzeek Date: 2014-07-15 00:28:07 Summary: - Fixed bug where multi-valued :class:`.Insert` construct would fail to check subsequent values entries beyond the first one given for literal SQL expressions. fixes #3069 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6fad9651b722/ Changeset: 6fad9651b722 Branch: None User: zzzeek Date: 2014-07-15 00:28:23 Summary: - Fixed bug where multi-valued :class:`.Insert` construct would fail to check subsequent values entries beyond the first one given for literal SQL expressions. fixes #3069 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/461993641704/ Changeset: 461993641704 Branch: None User: zzzeek Date: 2014-07-15 00:34:32 Summary: -Fixed bug in common table expressions whereby positional bound parameters could be expressed in the wrong final order when CTEs were nested in certain ways. fixes #3090 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/da46b015f075/ Changeset: da46b015f075 Branch: None User: zzzeek Date: 2014-07-15 00:34:52 Summary: -Fixed bug in common table expressions whereby positional bound parameters could be expressed in the wrong final order when CTEs were nested in certain ways. fixes #3090 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/ec40a84d96e4/ Changeset: ec40a84d96e4 Branch: None User: zzzeek Date: 2014-07-15 00:49:06 Summary: - Fixed a regression from 0.9.0 due to :ticket:`2736` where the :meth:`.Query.select_from` method no longer set up the "from entity" of the :class:`.Query` object correctly, so that subsequent :meth:`.Query.filter_by` or :meth:`.Query.join` calls would fail to check the appropriate "from" entity when searching for attributes by string name. fixes #3083 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/87a4ebf8af84/ Changeset: 87a4ebf8af84 Branch: None User: zzzeek Date: 2014-07-15 00:49:32 Summary: - Fixed a regression from 0.9.0 due to :ticket:`2736` where the :meth:`.Query.select_from` method no longer set up the "from entity" of the :class:`.Query` object correctly, so that subsequent :meth:`.Query.filter_by` or :meth:`.Query.join` calls would fail to check the appropriate "from" entity when searching for attributes by string name. fixes #3083 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0add251ea0be/ Changeset: 0add251ea0be Branch: None User: zzzeek Date: 2014-07-15 00:54:23 Summary: - In the SQL Server pyodbc dialect, repaired the implementation for the ``description_encoding`` dialect parameter, which when not explicitly set was preventing cursor.description from being parsed correctly in the case of result sets that contained names in alternate encodings. This parameter shouldn't be needed going forward. fixes #3091 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a1d9c81f5ac7/ Changeset: a1d9c81f5ac7 Branch: None User: zzzeek Date: 2014-07-15 00:55:02 Summary: - In the SQL Server pyodbc dialect, repaired the implementation for the ``description_encoding`` dialect parameter, which when not explicitly set was preventing cursor.description from being parsed correctly in the case of result sets that contained names in alternate encodings. This parameter shouldn't be needed going forward. fixes #3091 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a81d3a23c005/ Changeset: a81d3a23c005 Branch: None User: zzzeek Date: 2014-07-15 00:57:25 Summary: - In the SQL Server pyodbc dialect, repaired the implementation for the ``description_encoding`` dialect parameter, which when not explicitly set was preventing cursor.description from being parsed correctly in the case of result sets that contained names in alternate encodings. This parameter shouldn't be needed going forward. fixes #3091 Conflicts: test/sql/test_unicode.py Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/2825730e7be6/ Changeset: 2825730e7be6 Branch: None User: zzzeek Date: 2014-07-15 01:02:20 Summary: - Added statement encoding to the "SET IDENTITY_INSERT" statements which operate when an explicit INSERT is being interjected into an IDENTITY column, to support non-ascii table identifiers on drivers such as pyodbc + unix + py2k that don't support unicode statements. ref #3091 as this fix is also in that issue's patch, but is a different issue. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/1604b5c08917/ Changeset: 1604b5c08917 Branch: None User: zzzeek Date: 2014-07-15 01:03:40 Summary: - Added statement encoding to the "SET IDENTITY_INSERT" statements which operate when an explicit INSERT is being interjected into an IDENTITY column, to support non-ascii table identifiers on drivers such as pyodbc + unix + py2k that don't support unicode statements. ref #3091 as this fix is also in that issue's patch, but is a different issue. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/74d38623ff52/ Changeset: 74d38623ff52 Branch: rel_0_8 User: zzzeek Date: 2014-07-15 01:03:59 Summary: - Added statement encoding to the "SET IDENTITY_INSERT" statements which operate when an explicit INSERT is being interjected into an IDENTITY column, to support non-ascii table identifiers on drivers such as pyodbc + unix + py2k that don't support unicode statements. ref #3091 as this fix is also in that issue's patch, but is a different issue. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6fd0bc7c6284/ Changeset: 6fd0bc7c6284 Branch: None User: zzzeek Date: 2014-07-15 01:16:11 Summary: - Fixed a regression from 0.9.5 caused by :ticket:`3025` where the query used to determine "default schema" is invalid in SQL Server 2000. For SQL Server 2000 we go back to defaulting to the "schema name" parameter of the dialect, which is configurable but defaults to 'dbo'. fixes #3025 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c9a59575ebfd/ Changeset: c9a59575ebfd Branch: None User: zzzeek Date: 2014-07-15 01:16:42 Summary: - Fixed a regression from 0.9.5 caused by :ticket:`3025` where the query used to determine "default schema" is invalid in SQL Server 2000. For SQL Server 2000 we go back to defaulting to the "schema name" parameter of the dialect, which is configurable but defaults to 'dbo'. fixes #3025 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d2193f53c10d/ Changeset: d2193f53c10d Branch: None User: zzzeek Date: 2014-07-15 02:26:38 Summary: - Fix bug in naming convention feature where using a check constraint convention that includes ``constraint_name`` would then force all :class:`.Boolean` and :class:`.Enum` types to require names as well, as these implicitly create a constraint, even if the ultimate target backend were one that does not require generation of the constraint such as Postgresql. The mechanics of naming conventions for these particular constraints has been reorganized such that the naming determination is done at DDL compile time, rather than at constraint/table construction time. fixes #3067 Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d462dbde9976/ Changeset: d462dbde9976 Branch: rel_0_9 User: zzzeek Date: 2014-07-15 02:27:16 Summary: - Fix bug in naming convention feature where using a check constraint convention that includes ``constraint_name`` would then force all :class:`.Boolean` and :class:`.Enum` types to require names as well, as these implicitly create a constraint, even if the ultimate target backend were one that does not require generation of the constraint such as Postgresql. The mechanics of naming conventions for these particular constraints has been reorganized such that the naming determination is done at DDL compile time, rather than at constraint/table construction time. fixes #3067 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...> - 2014-07-14 22:12:11
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a49ec1cf7788/ Changeset: a49ec1cf7788 Branch: None User: zzzeek Date: 2014-07-15 00:09:54 Summary: - Added a "str()" step to the dialect_kwargs iteration for Python version < 2.6.5, working around the "no unicode keyword arg" bug as these args are passed along as keyword args within some reflection processes. fixes #3123 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c6de724785df/ Changeset: c6de724785df Branch: None User: zzzeek Date: 2014-07-15 00:10:34 Summary: need a 1.0.0 here Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/aba5b6e5c28c/ Changeset: aba5b6e5c28c Branch: None User: zzzeek Date: 2014-07-15 00:11:20 Summary: - Added a "str()" step to the dialect_kwargs iteration for Python version < 2.6.5, working around the "no unicode keyword arg" bug as these args are passed along as keyword args within some reflection processes. fixes #3123 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/110801750ebc/ Changeset: 110801750ebc Branch: rel_0_9 User: zzzeek Date: 2014-07-15 00:11:20 Summary: need a 1.0.0 here 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...> - 2014-07-14 20:31:54
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/5ec6ec9cbb1c/ Changeset: 5ec6ec9cbb1c Branch: None User: zzzeek Date: 2014-07-14 22:31:16 Summary: - add some order bys Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f2a9d522654d/ Changeset: f2a9d522654d Branch: rel_0_9 User: zzzeek Date: 2014-07-14 22:31:34 Summary: - add some order bys Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8be54fe1de23/ Changeset: 8be54fe1de23 Branch: rel_0_8 User: zzzeek Date: 2014-07-14 22:31:39 Summary: - add some order bys 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...> - 2014-07-14 15:34:07
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/81ceddf03e85/ Changeset: 81ceddf03e85 Branch: rel_0_9 User: zzzeek Date: 2014-07-14 17:33:27 Summary: - ensure usedevelop is present so that C exts are in the tests Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/897a567eb107/ Changeset: 897a567eb107 Branch: None User: zzzeek Date: 2014-07-14 17:33:46 Summary: - ensure usedevelop is present so that C exts are in the tests 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...> - 2014-07-14 03:59:46
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/aacf952e0b9a/ Changeset: aacf952e0b9a Branch: None User: zzzeek Date: 2014-07-14 05:59:12 Summary: - adjust this to work on PG also Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/2c41a702adca/ Changeset: 2c41a702adca Branch: rel_0_9 User: zzzeek Date: 2014-07-14 05:59:27 Summary: - adjust this to work on PG also Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/703cda62d754/ Changeset: 703cda62d754 Branch: rel_0_8 User: zzzeek Date: 2014-07-14 05:59:32 Summary: - adjust this to work on PG also 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...> - 2014-07-14 00:21:33
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/28dd15081db4/ Changeset: 28dd15081db4 Branch: None User: celttechie Date: 2014-07-14 02:10:55 Summary: PEP8 style fixes Affected #: 38 files https://bitbucket.org/zzzeek/sqlalchemy/commits/598e2311bf19/ Changeset: 598e2311bf19 Branch: None User: zzzeek Date: 2014-07-14 02:19:25 Summary: Merge branch 'pep8' Affected #: 36 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c4b838248150/ Changeset: c4b838248150 Branch: rel_0_9 User: celttechie Date: 2014-07-14 02:21:06 Summary: PEP8 style fixes Affected #: 36 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...> - 2014-07-13 23:01:37
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/071a18309858/ Changeset: 071a18309858 Branch: None User: zzzeek Date: 2014-07-14 00:55:18 Summary: - Fixed bug in :class:`.Enum` and other :class:`.SchemaType` subclasses where direct association of the type with a :class:`.MetaData` would lead to a hang when events (like create events) were emitted on the :class:`.MetaData`. fixes #3124 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/bd610650703f/ Changeset: bd610650703f Branch: rel_0_9 User: zzzeek Date: 2014-07-14 00:56:52 Summary: - Fixed bug in :class:`.Enum` and other :class:`.SchemaType` subclasses where direct association of the type with a :class:`.MetaData` would lead to a hang when events (like create events) were emitted on the :class:`.MetaData`. fixes #3124 Conflicts: test/sql/test_types.py Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/53b72c35f4e2/ Changeset: 53b72c35f4e2 Branch: rel_0_8 User: zzzeek Date: 2014-07-14 01:01:15 Summary: - Fixed bug in :class:`.Enum` and other :class:`.SchemaType` subclasses where direct association of the type with a :class:`.MetaData` would lead to a hang when events (like create events) were emitted on the :class:`.MetaData`. fixes #3124 Conflicts: lib/sqlalchemy/sql/sqltypes.py test/sql/test_types.py 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...> - 2014-07-11 00:49:06
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f02003aff7fb/ Changeset: f02003aff7fb Branch: None User: zzzeek Date: 2014-07-11 02:48:34 Summary: OK use tox Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/e31672952631/ Changeset: e31672952631 Branch: rel_0_9 User: zzzeek Date: 2014-07-11 02:48:35 Summary: update test runners to be module-based 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...> - 2014-07-11 00:42:10
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/6922a56140d9/ Changeset: 6922a56140d9 Branch: master User: zzzeek Date: 2014-07-11 02:41:48 Summary: update test runners to be module-based 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...> - 2014-07-11 00:29:13
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9281e7001caa/ Changeset: 9281e7001caa Branch: master User: zzzeek Date: 2014-07-11 02:06:47 Summary: OK use tox 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...> - 2014-07-10 22:52:16
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/304e5b2a1170/ Changeset: 304e5b2a1170 Branch: None User: celttechie Date: 2014-07-11 00:28:49 Summary: fixed style to conform to PEP8 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/600e6bfb3fa2/ Changeset: 600e6bfb3fa2 Branch: None User: celttechie Date: 2014-07-11 00:31:07 Summary: Merge branch 'master' of https://github.com/celttechie/sqlalchemy Pulling from new fork of SQLAlchemy Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a5aafc293bfa/ Changeset: a5aafc293bfa Branch: rel_0_9 User: celttechie Date: 2014-07-11 00:50:33 Summary: fixed style to conform to PEP8 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...> - 2014-07-10 20:11:22
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fc7081cc3df8/ Changeset: fc7081cc3df8 Branch: rel_0_9 User: zzzeek Date: 2014-07-10 22:10:46 Summary: - determine the root cause of the mysqlconnector issue, report it and move on Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/0190ede10767/ Changeset: 0190ede10767 Branch: None User: zzzeek Date: 2014-07-10 22:11:03 Summary: - determine the root cause of the mysqlconnector issue, report it and move on 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...> - 2014-07-10 15:48:27
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/6c81c4c26e29/ Changeset: 6c81c4c26e29 Branch: None User: zzzeek Date: 2014-07-10 17:47:31 Summary: - mark tests failing for mysqlconnector, oursql Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/6c2e5af39cdf/ Changeset: 6c2e5af39cdf Branch: rel_0_9 User: zzzeek Date: 2014-07-10 17:48:10 Summary: - mark tests failing for mysqlconnector, oursql Conflicts: test/dialect/mysql/test_types.py 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...> - 2014-07-10 15:37:47
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ef968470c9a6/ Changeset: ef968470c9a6 Branch: None User: zzzeek Date: 2014-07-10 17:36:57 Summary: imports gone bad 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...> - 2014-07-10 15:27:00
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e5d0fa94937b/ Changeset: e5d0fa94937b Branch: None User: zzzeek Date: 2014-07-10 17:26:13 Summary: - The :meth:`.TypeEngine.with_variant` method will now accept a type class as an argument which is internally converted to an instance, using the same convention long established by other constructs such as :class:`.Column`. fixes #3122 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6ef47a46c1cd/ Changeset: 6ef47a46c1cd Branch: rel_0_9 User: zzzeek Date: 2014-07-10 17:26:42 Summary: - The :meth:`.TypeEngine.with_variant` method will now accept a type class as an argument which is internally converted to an instance, using the same convention long established by other constructs such as :class:`.Column`. fixes #3122 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...> - 2014-07-09 23:01:27
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/723d118ef1c4/ Changeset: 723d118ef1c4 Branch: rel_0_9 User: zzzeek Date: 2014-07-10 00:29:17 Summary: - break up the <authors> copyright comment as part of a pass to get all flake8 passing Affected #: 163 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.
