sqlalchemy-commits Mailing List for SQLAlchemy (Page 69)
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-03-28 23:20:16
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3bb9de09aa1e/ Changeset: 3bb9de09aa1e Branch: rel_0_8 User: zzzeek Date: 2014-03-29 00:17:04 Summary: this doesnt need sane multi row now... Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/6983e1479021/ Changeset: 6983e1479021 Branch: None User: zzzeek Date: 2014-03-29 00:19:55 Summary: dont need rowcount 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-03-28 22:01:24
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/477b9e7f0297/ Changeset: 477b9e7f0297 Branch: None User: zzzeek Date: 2014-03-28 22:26:45 Summary: mark failing tests for buggy mysqlconnector Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a0329f71ad48/ Changeset: a0329f71ad48 Branch: None User: zzzeek Date: 2014-03-28 22:42:55 Summary: - revert part of c01558ae7f4a for now as we also test that a DELETE of two rows where one is to be deleted from ON DELETE CASCADE succeeds; the check here makes that fail. We will need to add an option to enable/disable this check per mapping, will likely do this in next version Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7473b5457497/ Changeset: 7473b5457497 Branch: rel_0_8 User: zzzeek Date: 2014-03-28 22:44:23 Summary: - revert part of c01558ae7f4a for now as we also test that a DELETE of two rows where one is to be deleted from ON DELETE CASCADE succeeds; the check here makes that fail. We will need to add an option to enable/disable this check per mapping, will likely do this in next version Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d6618e411955/ Changeset: d6618e411955 Branch: None User: zzzeek Date: 2014-03-28 23:00:35 Summary: - Added new parameter :paramref:`.mapper.confirm_deleted_rows`. Defaults to True, indicates that a series of DELETE statements should confirm that the cursor rowcount matches the number of primary keys that should have matched; this behavior had been taken off in most cases (except when version_id is used) to support the unusual edge case of self-referential ON DELETE CASCADE; to accomodate this, the message is now just a warning, not an exception, and the flag can be used to indicate a mapping that expects self-refererntial cascaded deletes of this nature. See also :ticket:`2403` for background on the original change. re: #2403 fix #3007 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-03-28 21:15:36
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/91de02cc668a/ Changeset: 91de02cc668a Branch: rel_0_8 User: zzzeek Date: 2014-03-28 21:48:05 Summary: revert inadvertent pdb Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9a49d5fea5a9/ Changeset: 9a49d5fea5a9 Branch: None User: zzzeek Date: 2014-03-28 21:48:20 Summary: revert inadvertent pdb 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-03-28 20:47:52
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/094a8550f184/ Changeset: 094a8550f184 Branch: None User: zzzeek Date: 2014-03-28 21:47:12 Summary: - the rewording of orderinglist docs got committed by accident, finish it up Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/b4eeebbabebc/ Changeset: b4eeebbabebc Branch: rel_0_8 User: zzzeek Date: 2014-03-28 21:47:38 Summary: - the rewording of orderinglist docs got committed by accident, finish it up 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-03-28 20:41:52
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c01558ae7f4a/ Changeset: c01558ae7f4a Branch: None User: zzzeek Date: 2014-03-28 21:32:11 Summary: - Fixed ORM bug where changing the primary key of an object, then marking it for DELETE would fail to target the correct row for DELETE. Then to compound matters, basic "number of rows matched" checks were not being performed. Both issues are fixed, however note that the "rows matched" check requires so-called "sane multi-row count" functionality; the DBAPI's executemany() method must count up the rows matched by individual statements and SQLAlchemy's dialect must mark this feature as supported, currently applies to some mysql dialects, psycopg2, sqlite only. fixes #3006 - Enabled "sane multi-row count" checking for the psycopg2 DBAPI, as this seems to be supported as of psycopg2 2.0.9. Affected #: 10 files https://bitbucket.org/zzzeek/sqlalchemy/commits/e789a75f9a32/ Changeset: e789a75f9a32 Branch: rel_0_8 User: zzzeek Date: 2014-03-28 21:34:54 Summary: - Fixed ORM bug where changing the primary key of an object, then marking it for DELETE would fail to target the correct row for DELETE. Then to compound matters, basic "number of rows matched" checks were not being performed. Both issues are fixed, however note that the "rows matched" check requires so-called "sane multi-row count" functionality; the DBAPI's executemany() method must count up the rows matched by individual statements and SQLAlchemy's dialect must mark this feature as supported, currently applies to some mysql dialects, psycopg2, sqlite only. fixes #3006 - Enabled "sane multi-row count" checking for the psycopg2 DBAPI, as this seems to be supported as of psycopg2 2.0.9. Conflicts: test/orm/test_naturalpks.py test/requirements.py Affected #: 10 files https://bitbucket.org/zzzeek/sqlalchemy/commits/28aaa5938797/ Changeset: 28aaa5938797 Branch: None User: zzzeek Date: 2014-03-28 21:36:11 Summary: - fix set syntax supposed to be dict Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a04fb820289d/ Changeset: a04fb820289d Branch: None User: zzzeek Date: 2014-03-28 21:37:43 Summary: pickle of execption not supported on mysqlconnector Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9c731b2ebf49/ Changeset: 9c731b2ebf49 Branch: None User: zzzeek Date: 2014-03-28 21:41:08 Summary: - add further coverage for join_condition to make sure we get this case where there are multiple, equivalent foreign keys 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-03-28 15:06:07
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9cdbed37f8c4/ Changeset: 9cdbed37f8c4 Branch: None User: zzzeek Date: 2014-03-28 16:05:46 Summary: clarify doc 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-03-28 15:03:16
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/610e0594e249/ Changeset: 610e0594e249 Branch: None User: zzzeek Date: 2014-03-28 16:02:34 Summary: - fix py3k bug re: dictionary values(), fixes #3005 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-03-28 14:50:10
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4d93a52e7789/ Changeset: 4d93a52e7789 Branch: None User: zzzeek Date: 2014-03-28 15:49:37 Summary: - Added support to automap for the case where a relationship should not be created between two classes that are in a joined inheritance relationship, for those foreign keys that link the subclass back to the superclass. fixes #3004 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-03-28 00:39:42
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/825d3b0d6db4/ Changeset: 825d3b0d6db4 Branch: None User: zzzeek Date: 2014-03-28 01:38:46 Summary: - Fixed a very old behavior where the lazy load emitted for a one-to-many could inappropriately pull in the parent table, and also return results inconsistent based on what's in the parent table, when the primaryjoin includes some kind of discriminator against the parent table, such as ``and_(parent.id == child.parent_id, parent.deleted == False)``. While this primaryjoin doesn't make that much sense for a one-to-many, it is slightly more common when applied to the many-to-one side, and the one-to-many comes as a result of a backref. Loading rows from ``child`` in this case would keep ``parent.deleted == False`` as is within the query, thereby yanking it into the FROM clause and doing a cartesian product. The new behavior will now substitute the value of the local "parent.deleted" for that parameter as is appropriate. Though typically, a real-world app probably wants to use a different primaryjoin for the o2m side in any case. fixes #2948 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-03-27 23:43:51
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0611baa88919/ Changeset: 0611baa88919 Branch: None User: zzzeek Date: 2014-03-28 00:43:15 Summary: - Improved the check for "how to join from A to B" such that when a table has multiple, composite foreign keys targeting a parent table, the :paramref:`.relationship.foreign_keys` argument will be properly interpreted in order to resolve the ambiguity; previously this condition would raise that there were multiple FK paths when in fact the foreign_keys argument should be establishing which one is expected. fixes #2965 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-03-27 23:19:04
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/50576a01eb39/ Changeset: 50576a01eb39 Branch: None User: zzzeek Date: 2014-03-28 00:18:06 Summary: - Tweaked the settings for mysql-connector-python; in Py2K, the "supports unicode statements" flag is now False, so that SQLAlchemy will encode the *SQL string* (note: *not* the parameters) to bytes before sending to the database. This seems to allow all unicode-related tests to pass for mysql-connector, including those that use non-ascii table/column names, as well as some tests for the TEXT type using unicode under cursor.executemany(). - other mysql-connector fixes; latest version seems to do better on function call counts Affected #: 7 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |
|
From: Bitbucket <com...@bi...> - 2014-03-27 22:28:54
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/eb94838c72f5/ Changeset: eb94838c72f5 Branch: None User: Stefan Reich Date: 2014-03-26 16:04:23 Summary: Added missing text_type requirement to TextTest Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/460139f630a8/ Changeset: 460139f630a8 Branch: None User: Stefan Reich Date: 2014-03-27 23:28:28 Summary: Added missing text_type requirement to TextTest Conflicts: lib/sqlalchemy/testing/suite/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-03-27 17:18:20
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e3a1a2d01c83/ Changeset: e3a1a2d01c83 Branch: master User: zzzeek Date: 2014-03-27 18:17:20 Summary: - fixes to multi-backend tests - move the logic to determine "test id" into plugin_base - update callcounts 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-03-27 00:43:40
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b6411ee3cfe6/ Changeset: b6411ee3cfe6 Branch: None User: zzzeek Date: 2014-03-27 01:43:20 Summary: fixes to get profiling tests working again 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-03-26 23:16:13
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/bd86942b0586/ Changeset: bd86942b0586 Branch: None User: zzzeek Date: 2014-03-27 00:15:49 Summary: dont warn, that just crashes the test... 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-03-26 20:52:26
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/99d07abe1704/ Changeset: 99d07abe1704 Branch: None User: zzzeek Date: 2014-03-26 21:52:04 Summary: try to liberalize the pool._refs assertion a bit 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-03-26 20:40:07
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a465f3d031f0/ Changeset: a465f3d031f0 Branch: None User: zzzeek Date: 2014-03-26 21:39:43 Summary: use integer division 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-03-26 20:34:16
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/761c8ff15de1/ Changeset: 761c8ff15de1 Branch: None User: zzzeek Date: 2014-03-26 21:31:52 Summary: - work on fixing some race-condition failures: 1. make sure pool._invalidate() sets the timestamp up before invalidating the target connection. we can otherwise show how the conn.invalidate() + pool._invalidate() can lead to an extra connection being made. 2. to help with that, soften up the check on connection.invalidate() when connection is already closed. a warning is fine here 3. add a mutex to test_max_overflow() when we connect, because the way we're using mock depends on an iterator, that needs to be synchronized 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-03-26 19:31:00
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/dc0d581d5d10/ Changeset: dc0d581d5d10 Branch: None User: zzzeek Date: 2014-03-26 20:18:29 Summary: - rework memusage tests so that it only runs five iterations at a time, if it sees success within that period, it's done. memusage tests have become very slow 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-03-26 18:43:35
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4100f9c06e86/ Changeset: 4100f9c06e86 Branch: None User: zzzeek Date: 2014-03-26 19:42:51 Summary: - remove nose dependency 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-03-25 16:28:28
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/1a35188b6903/ Changeset: 1a35188b6903 Branch: None User: zzzeek Date: 2014-03-25 17:26:42 Summary: - Fixed regression caused by release 0.8.5 / 0.9.3's compatibility enhancements where index reflection on Postgresql versions specific to only the 8.1, 8.2 series again broke, surrounding the ever problematic int2vector type. While int2vector supports array operations as of 8.1, apparently it only supports CAST to a varchar as of 8.3. fix #3000 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/f6614aed6604/ Changeset: f6614aed6604 Branch: rel_0_8 User: zzzeek Date: 2014-03-25 17:27:03 Summary: - Fixed regression caused by release 0.8.5 / 0.9.3's compatibility enhancements where index reflection on Postgresql versions specific to only the 8.1, 8.2 series again broke, surrounding the ever problematic int2vector type. While int2vector supports array operations as of 8.1, apparently it only supports CAST to a varchar as of 8.3. fix #3000 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-03-24 23:31:28
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/74f7509d6636/ Changeset: 74f7509d6636 Branch: None User: zzzeek Date: 2014-03-25 00:30:44 Summary: add some more mock structure so tricky DBAPIs like pypy work 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-03-24 17:34:24
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/12c8a10b81a4/ Changeset: 12c8a10b81a4 Branch: None User: zzzeek Date: 2014-03-24 18:33:53 Summary: fix 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-03-24 16:50:04
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/50d19f55d265/ Changeset: 50d19f55d265 Branch: None User: zzzeek Date: 2014-03-24 17:49:22 Summary: - add some more rules to make sure all tests run if DBs are available 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-03-24 16:12:57
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/990266f5515a/ Changeset: 990266f5515a Branch: None User: zzzeek Date: 2014-03-24 17:12:26 Summary: fix some mysqlconnector failures 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. |
737 messages has been excluded from this view by a project administrator.
