sqlalchemy-commits Mailing List for SQLAlchemy (Page 73)
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-02-24 20:26:31
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fd381adbcb83/ Changeset: fd381adbcb83 Branch: master User: zzzeek Date: 2014-02-24 21:24:28 Summary: 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-02-24 20:21:57
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7ae76ffacd1c/ Changeset: 7ae76ffacd1c Branch: master User: zzzeek Date: 2014-02-24 21:21:38 Summary: 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-02-24 18:00:37
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/1122d355d15a/ Changeset: 1122d355d15a Branch: None User: zzzeek Date: 2014-02-24 18:59:32 Summary: - we're testing a query here with non-standard aliasing which fails on PG and MySQL. Leave this test in place as its ultimately a SQLite use case, but only test on SQLite. We perhaps should add another test case that works on all platforms. 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-02-24 17:52:42
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d966920b3df2/ Changeset: d966920b3df2 Branch: None User: zzzeek Date: 2014-02-24 18:52:12 Summary: - Fixed regression from 0.8 where using an option like :func:`.orm.lazyload` with the "wildcard" expression, e.g. ``"*"``, would raise an assertion error in the case where the query didn't contain any actual entities. This assertion is meant for other cases and was catching this one inadvertently. 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-02-24 17:35:33
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/537d92129386/ Changeset: 537d92129386 Branch: None User: zzzeek Date: 2014-02-24 18:34:54 Summary: - Fixed bug in the versioned_history example where column-level INSERT defaults would prevent history values of NULL from being written. 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-02-24 04:06:07
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8b58c6adc2f0/ Changeset: 8b58c6adc2f0 Branch: None User: zzzeek Date: 2014-02-24 05:05:29 Summary: more detail, what actually loads, etc. 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-02-23 21:30:38
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/948b14b65b96/ Changeset: 948b14b65b96 Branch: None User: zzzeek Date: 2014-02-23 22:30:09 Summary: -rewrite expire/refresh section 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-02-23 02:40:50
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/122ae490655b/ Changeset: 122ae490655b Branch: master User: zzzeek Date: 2014-02-23 03:39:14 Summary: no more wheels until they have a point fixes #2970 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-02-20 21:16:27
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ceaa6047ef8b/ Changeset: ceaa6047ef8b Branch: master User: zzzeek Date: 2014-02-20 22:14:29 Summary: - More fixes to SQLite "join rewriting"; the fix from :ticket:`2967` implemented right before the release of 0.9.3 affected the case where a UNION contained nested joins in it. "Join rewriting" is a feature with a wide range of possibilities and is the first intricate "SQL rewriting" feature we've introduced in years, so we're sort of going through a lot of iterations with it (not unlike eager loading back in the 0.2/0.3 series, polymorphic loading in 0.4/0.5). We should be there soon so thanks for bearing with us :). fixes #2969 re: #2967 - solve the issue of join rewriting inspecting various types of from objects without using isinstance(), by adding some new underscored inspection flags to the FromClause hierarchy. 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-02-20 04:26:51
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/39c0485a2115/ Changeset: 39c0485a2115 Branch: None User: zzzeek Date: 2014-02-20 04:56:06 Summary: 2014 Affected #: 134 files https://bitbucket.org/zzzeek/sqlalchemy/commits/1366ef9f1cbb/ Changeset: 1366ef9f1cbb Branch: rel_0_8 User: zzzeek Date: 2014-02-20 04:59:11 Summary: 0.8.5 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/b2fd85b7d5aa/ Changeset: b2fd85b7d5aa Branch: None User: zzzeek Date: 2014-02-20 05:01:40 Summary: 0.9.3 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/5634a3f104de/ Changeset: 5634a3f104de Branch: None User: zzzeek Date: 2014-02-20 05:05:06 Summary: 0.8.5 released same day Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/5c88f38c7259/ Changeset: 5c88f38c7259 Branch: None User: zzzeek Date: 2014-02-20 05:09:07 Summary: fix typo 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-02-20 01:34:14
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0c3fdb808a48/ Changeset: 0c3fdb808a48 Branch: rel_0_8 User: zzzeek Date: 2014-02-20 02:33:31 Summary: - isolate this failure as only on 0.8, only in py3.3, just comment it out, not really worth tracking down 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-02-20 01:16:18
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a4f1d2ec6e80/ Changeset: a4f1d2ec6e80 Branch: None User: zzzeek Date: 2014-02-20 02:15:30 Summary: skip this on oracle 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-02-20 00:23:53
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/57b214a0a446/ Changeset: 57b214a0a446 Branch: None User: zzzeek Date: 2014-02-20 01:22:17 Summary: - Added an additional message to psycopg2 disconnect detection, "could not send data to server", which complements the existing "could not receive data from server" and has been observed by users, fixes #2936 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/cd0d29cef4c6/ Changeset: cd0d29cef4c6 Branch: rel_0_8 User: zzzeek Date: 2014-02-20 01:22:48 Summary: - Added an additional message to psycopg2 disconnect detection, "could not send data to server", which complements the existing "could not receive data from server" and has been observed by users, fixes #2936 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-02-20 00:14:01
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/25831872db7f/ Changeset: 25831872db7f Branch: None User: zzzeek Date: 2014-02-20 01:04:04 Summary: - Fixed bug in SQLite "join rewriting" where usage of an exists() construct would fail to be rewritten properly, such as when the exists is mapped to a column_property in an intricate nested-join scenario. #2967 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/69d1d08dc398/ Changeset: 69d1d08dc398 Branch: None User: zzzeek Date: 2014-02-20 01:12:40 Summary: - re: #2967, also fixed a somewhat related issue where join rewriting would fail on the columns clause of the SELECT statement if the targets were aliased tables, as opposed to individual aliased columns. 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-02-19 22:02:01
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a0fb9e74c61b/ Changeset: a0fb9e74c61b Branch: None User: zzzeek Date: 2014-02-19 23:00:37 Summary: - add a topological rule here to place PARTITIONS after PARTITION_BY, for output consistency within the tests as well as in practice Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/bfdb51ac6a4b/ Changeset: bfdb51ac6a4b Branch: rel_0_8 User: zzzeek Date: 2014-02-19 23:01:26 Summary: - add a topological rule here to place PARTITIONS after PARTITION_BY, for output consistency within the tests as well as in practice 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-02-19 21:13:26
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8878e2307954/ Changeset: 8878e2307954 Branch: None User: zzzeek Date: 2014-02-19 22:11:19 Summary: restore the check ahead of the lock to avoid using it after initialization is done Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f9059f6cd8cc/ Changeset: f9059f6cd8cc Branch: rel_0_8 User: zzzeek Date: 2014-02-19 22:12:36 Summary: restore check ahead of the lock to avoid locking when not needed 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-02-19 21:07:48
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4f29ebc72866/ Changeset: 4f29ebc72866 Branch: None User: zzzeek Date: 2014-02-19 22:02:29 Summary: - Support has been improved for Postgresql reflection behavior on very old (pre 8.1) versions of Postgresql, and potentially other PG engines such as Redshift (assuming Redshift reports the version as < 8.1). The query for "indexes" as well as "primary keys" relies upon inspecting a so-called "int2vector" datatype, which refuses to coerce to an array prior to 8.1 causing failures regarding the "ANY()" operator used in the query. Extensive googling has located the very hacky, but recommended-by-PG-core-developer query to use when PG version < 8.1 is in use, so index and primary key constraint reflection now work on these versions. Conflicts: doc/build/changelog/changelog_09.rst test/dialect/postgresql/test_types.py Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/033463cd4bd9/ Changeset: 033463cd4bd9 Branch: None User: zzzeek Date: 2014-02-19 22:03:05 Summary: backport Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0d81c6c7a311/ Changeset: 0d81c6c7a311 Branch: rel_0_8 User: zzzeek Date: 2014-02-19 22:07:01 Summary: - add improved support here for string parsing of predicates, backport from 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-02-19 20:55:56
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a552606091bf/ Changeset: a552606091bf Branch: None User: zzzeek Date: 2014-02-19 21:49:37 Summary: - Added new MySQL-specific :class:`.mysql.DATETIME` which includes fractional seconds support; also added fractional seconds support to :class:`.mysql.TIMESTAMP`. DBAPI support is limited, though fractional seconds are known to be supported by MySQL Connector/Python. Patch courtesy Geert JM Vanderkelen. #2941 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/dd6884eafaaf/ Changeset: dd6884eafaaf Branch: rel_0_8 User: zzzeek Date: 2014-02-19 21:49:59 Summary: - Added new MySQL-specific :class:`.mysql.DATETIME` which includes fractional seconds support; also added fractional seconds support to :class:`.mysql.TIMESTAMP`. DBAPI support is limited, though fractional seconds are known to be supported by MySQL Connector/Python. Patch courtesy Geert JM Vanderkelen. #2941 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-02-19 20:28:14
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c597843f137b/ Changeset: c597843f137b Branch: None User: Marcus McCurdy Date: 2014-02-14 19:23:51 Summary: Fixes MySQL dialect partitioning Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7e66d7e39213/ Changeset: 7e66d7e39213 Branch: None User: zzzeek Date: 2014-02-19 21:24:36 Summary: Merge branch 'master' of https://bitbucket.org/50onred/sqlalchemy/overview into t Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0b4c0384f60f/ Changeset: 0b4c0384f60f Branch: None User: zzzeek Date: 2014-02-19 21:26:51 Summary: changelog for pullreq 12 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/17d7e98b5e14/ Changeset: 17d7e98b5e14 Branch: None User: Marcus McCurdy Date: 2014-02-19 21:27:24 Summary: Fixes MySQL dialect partitioning Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/56364c636e00/ Changeset: 56364c636e00 Branch: rel_0_8 User: zzzeek Date: 2014-02-19 21:27:31 Summary: changelog for pullreq 12 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-02-19 20:23:56
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/77ed03652580/ Changeset: 77ed03652580 Branch: None User: zzzeek Date: 2014-02-19 21:18:22 Summary: - Fixed bug where calling :meth:`.Insert.values` with an empty list or tuple would raise an IndexError. It now produces an empty insert construct as would be the case with an empty dictionary. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/506817a84e6b/ Changeset: 506817a84e6b Branch: rel_0_8 User: zzzeek Date: 2014-02-19 21:23:04 Summary: - Fixed bug where calling :meth:`.Insert.values` with an empty list or tuple would raise an IndexError. It now produces an empty insert construct as would be the case with an empty dictionary. Conflicts: lib/sqlalchemy/sql/dml.py 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-02-19 15:52:37
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/dd32540dabbe/ Changeset: dd32540dabbe Branch: None User: zzzeek Date: 2014-02-19 16:48:32 Summary: - Fixed a critical regression caused by :ticket:`2880` where the newly concurrent ability to return connections from the pool means that the "first_connect" event is now no longer synchronized either, thus leading to dialect mis-configurations under even minimal concurrency situations. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4ac0558e1149/ Changeset: 4ac0558e1149 Branch: rel_0_8 User: zzzeek Date: 2014-02-19 16:51:57 Summary: - Fixed a critical regression caused by :ticket:`2880` where the newly concurrent ability to return connections from the pool means that the "first_connect" event is now no longer synchronized either, thus leading to dialect mis-configurations under even minimal concurrency situations. Conflicts: lib/sqlalchemy/event/attr.py 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-02-19 01:52:39
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/185938e7b746/ Changeset: 185938e7b746 Branch: None User: zzzeek Date: 2014-02-19 02:49:33 Summary: - update mysql connector python link, #2938 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/df288504d9f3/ Changeset: df288504d9f3 Branch: rel_0_8 User: zzzeek Date: 2014-02-19 02:50:06 Summary: - update mysql connector python link, #2938 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/c83a39e4f864/ Changeset: c83a39e4f864 Branch: rel_0_7 User: zzzeek Date: 2014-02-19 02:51:25 Summary: - update mysql connector python links, #2938 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/33397beb3ada/ Changeset: 33397beb3ada Branch: rel_0_6 User: zzzeek Date: 2014-02-19 02:51:51 Summary: - update mysql connector python links, #2938 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-02-18 23:36:05
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ecdfc31774e2/ Changeset: ecdfc31774e2 Branch: None User: zzzeek Date: 2014-02-19 00:35:23 Summary: - Support has been improved for Postgresql reflection behavior on very old (pre 8.1) versions of Postgresql, and potentially other PG engines such as Redshift (assuming Redshift reports the version as < 8.1). The query for "indexes" as well as "primary keys" relies upon inspecting a so-called "int2vector" datatype, which refuses to coerce to an array prior to 8.1 causing failures regarding the "ANY()" operator used in the query. Extensive googling has located the very hacky, but recommended-by-PG-core-developer query to use when PG version < 8.1 is in use, so index and primary key constraint reflection now work on these versions. 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-02-18 21:59:05
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fdedb69d9c6d/ Changeset: fdedb69d9c6d Branch: None User: zzzeek Date: 2014-02-18 22:58:14 Summary: update docs re: cx_oracle unicode as of 0.9.2, no more outputtypehandlers 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-02-17 21:03:49
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b4d9795db164/ Changeset: b4d9795db164 Branch: None User: zzzeek Date: 2014-02-17 22:03:07 Summary: - dont need this import and it's not in 2.6 anyway 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.
