sqlalchemy-commits Mailing List for SQLAlchemy (Page 46)
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...> - 2015-03-10 19:27:51
|
9 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/955576fcf6e7/ Changeset: 955576fcf6e7 Branch: None User: iurisilvio Date: 2015-02-26 00:05:31+00:00 Summary: Dialect option `postgresql_concurrently` to `Index` construct. Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7ac81f6d0a84/ Changeset: 7ac81f6d0a84 Branch: None User: zzzeek Date: 2015-03-10 19:00:21+00:00 Summary: Merge branch 'postgres-concurrently' of https://bitbucket.org/iurisilvio/sqlalchemy into pr45 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/5d1206c10a96/ Changeset: 5d1206c10a96 Branch: pr45 User: zzzeek Date: 2015-03-10 19:05:27+00:00 Summary: - changelog and docs for pullreq bitbucket:45 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/46f84f994456/ Changeset: 46f84f994456 Branch: None User: iurisilvio Date: 2015-03-10 19:06:14+00:00 Summary: Dialect option `postgresql_concurrently` to `Index` construct. (cherry picked from commit 955576fcf6e7aff7fe924ec3b33bb6d243ddd312) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d14f30f926d8/ Changeset: d14f30f926d8 Branch: None User: zzzeek Date: 2015-03-10 19:07:17+00:00 Summary: - changelog and docs for pullreq bitbucket:45 (cherry picked from commit 5d1206c10a96b6685e57baa9ae09f04f00cf425b) Conflicts: lib/sqlalchemy/dialects/postgresql/base.py Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/ff846286f2f6/ Changeset: ff846286f2f6 Branch: None User: zzzeek Date: 2015-03-10 19:16:02+00:00 Summary: - repair doclevel Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/587c85db7681/ Changeset: 587c85db7681 Branch: None User: zzzeek Date: 2015-03-10 19:16:19+00:00 Summary: - repair doclevel Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/50866d2f857d/ Changeset: 50866d2f857d Branch: None User: zzzeek Date: 2015-03-10 19:24:28+00:00 Summary: - copyright 2015 Affected #: 170 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c3c889d88260/ Changeset: c3c889d88260 Branch: rel_0_9 User: zzzeek Date: 2015-03-10 19:27:20+00:00 Summary: - copyright 2015 Affected #: 171 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...> - 2015-03-10 18:58:37
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9fee9cb87e0d/ Changeset: 9fee9cb87e0d Branch: None User: EvaSDK Date: 2015-03-10 18:28:50+00:00 Summary: Fix slice addressing of _AssociationList with python3 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/78874d3679fe/ Changeset: 78874d3679fe Branch: None User: zzzeek Date: 2015-03-10 18:54:20+00:00 Summary: - changelog for pr github:154 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9d617468a661/ Changeset: 9d617468a661 Branch: None User: EvaSDK Date: 2015-03-10 18:56:17+00:00 Summary: Fix dependencies for running coverage checks Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/c88900a3748c/ Changeset: c88900a3748c Branch: None User: EvaSDK Date: 2015-03-10 18:57:14+00:00 Summary: Fix slice addressing of _AssociationList with python3 (cherry picked from commit 9fee9cb87e0d13db4426664f5758c1ddad0533e3) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6d22831e1699/ Changeset: 6d22831e1699 Branch: rel_0_9 User: zzzeek Date: 2015-03-10 18:57:22+00:00 Summary: - changelog for pr github:154 (cherry picked from commit 78874d3679fe45275d44dda40f4f1bae9a0558b7) 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...> - 2015-03-10 18:22:53
|
7 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4a42bd5a2cba/ Changeset: 4a42bd5a2cba Branch: None User: groner Date: 2015-01-26 19:48:23+00:00 Summary: Test for partial index support in sqlite dialects. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/30ce7e93f406/ Changeset: 30ce7e93f406 Branch: None User: groner Date: 2015-01-26 19:50:24+00:00 Summary: Partial index support with sqlite dialects. >From https://www.sqlite.org/partialindex.html > Partial indexes have been supported in SQLite since version 3.8.0. Reflection does not expose the predicate of partial indexes. The postgresql dialect does detect such indexes and issue a warning. I looked into matching this level of support, but the sqlite pragma index_info does not expose the predicate. Getting this data would probably require parsing the CREATE INDEX statement from sqlite_master. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/ddf35e2f04c5/ Changeset: ddf35e2f04c5 Branch: None User: zzzeek Date: 2015-03-10 18:12:58+00:00 Summary: Merge branch 'sqlite-partial-indexes' of https://bitbucket.org/groner/sqlalchemy into pr42 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6ac0555eaa63/ Changeset: 6ac0555eaa63 Branch: None User: zzzeek Date: 2015-03-10 18:18:35+00:00 Summary: - changelog / doc for sqlite partial indexes Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6b108eea5219/ Changeset: 6b108eea5219 Branch: None User: groner Date: 2015-03-10 18:19:18+00:00 Summary: Partial index support with sqlite dialects. >From https://www.sqlite.org/partialindex.html > Partial indexes have been supported in SQLite since version 3.8.0. Reflection does not expose the predicate of partial indexes. The postgresql dialect does detect such indexes and issue a warning. I looked into matching this level of support, but the sqlite pragma index_info does not expose the predicate. Getting this data would probably require parsing the CREATE INDEX statement from sqlite_master. (cherry picked from commit 30ce7e93f4068b00ced0db785fdd578dc8a45975) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/2f379e490d60/ Changeset: 2f379e490d60 Branch: None User: groner Date: 2015-03-10 18:20:43+00:00 Summary: Test for partial index support in sqlite dialects. (cherry picked from commit 4a42bd5a2cba23782df7b6f98cadb7382d22498e) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d0881de1c480/ Changeset: d0881de1c480 Branch: None User: zzzeek Date: 2015-03-10 18:20:43+00:00 Summary: - changelog / doc for sqlite partial indexes (cherry picked from commit 6ac0555eaa6363ac9d0ad6566248dd294ad61d9e) 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...> - 2015-03-09 20:05:47
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9afe585f4599/ Changeset: 9afe585f4599 Branch: None User: zzzeek Date: 2015-03-09 18:36:23+00:00 Summary: - pick around gaining modest dings in callcounts here and there Affected #: 7 files https://bitbucket.org/zzzeek/sqlalchemy/commits/611d88d23431/ Changeset: 611d88d23431 Branch: None User: zzzeek Date: 2015-03-09 19:19:49+00:00 Summary: - add a callers option Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/adaa00330035/ Changeset: adaa00330035 Branch: None User: zzzeek Date: 2015-03-09 19:24:01+00:00 Summary: - reduce some callcounts related to the lightweight tuple, basically by caching them. - improve LRUCache so that size management only proceeds in one thread, add a real get() method Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/b8a39b8636c8/ Changeset: b8a39b8636c8 Branch: None User: zzzeek Date: 2015-03-09 19:24:37+00:00 Summary: - fix a potential race condition where the per-mapper LRUCache used by persistence.py could theoretically hit the limit of the cache (100 items by default) and at some points fail to have a key that we check for, due to the cleanup. This has never been observed so its likely that so far, the total number of INSERT, UPDATE and DELETE statement structures in real apps has not exceeded 100 on a per-mapper basis; this could happen for apps that run a very wide variety of attribute modified combinations into the unit of work, *and* which have very high concurrency going on. This change will be a lot more significant when we open up use of LRUCache + compiled cache with the baked query extension. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/26d598348936/ Changeset: 26d598348936 Branch: None User: zzzeek Date: 2015-03-09 20:02:55+00:00 Summary: - updated counts 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...> - 2015-03-09 17:07:52
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fdd2b42db59c/ Changeset: fdd2b42db59c Branch: None User: zzzeek Date: 2015-03-09 17:05:46+00:00 Summary: - we really don't want to force lib here, but we do need it for the plain "pytest" case, so do an append instead of an insert - add a new tox file to do a full regen of callcounts Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/fcfa62bd76ee/ Changeset: fcfa62bd76ee Branch: None User: zzzeek Date: 2015-03-09 17:07:09+00:00 Summary: - start locking down querying for cols after observing yesterdays callcount bump due to the slots thing - rewrite profiles using new technique 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...> - 2015-03-08 19:32:58
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a92f6662b4e1/ Changeset: a92f6662b4e1 Branch: None User: zzzeek Date: 2015-03-08 18:43:42+00:00 Summary: - add this for testing Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a421106c9d1d/ Changeset: a421106c9d1d Branch: None User: zzzeek Date: 2015-03-08 19:32:21+00:00 Summary: - random performance whacking vs. 0.9, in particular we have to watch for the slots-based __getattr__ thing getting hit 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...> - 2015-03-08 18:17:22
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7c9a0e18bead/ Changeset: 7c9a0e18bead Branch: None User: zzzeek Date: 2015-03-08 18:16:59+00:00 Summary: - fix some more result_map calls 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...> - 2015-03-08 16:34:18
|
6 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/251ebf4fee0f/ Changeset: 251ebf4fee0f Branch: None User: zzzeek Date: 2015-03-06 17:21:30+00:00 Summary: Patch to produce the fix for #2964 applied to rel_0_8_4 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/ef52a1eb2bc2/ Changeset: ef52a1eb2bc2 Branch: None User: zzzeek Date: 2015-03-06 17:26:08+00:00 Summary: Patch to produce the fix for #3101 applied to rel_0_8_4 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/259a54f2f77a/ Changeset: 259a54f2f77a Branch: None User: zzzeek Date: 2015-03-06 19:42:11+00:00 Summary: patch to allow tests to run under older nosetests Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/53ed475f12ed/ Changeset: 53ed475f12ed Branch: rel_0_8_4_dev User: zzzeek Date: 2015-03-06 21:02:04+00:00 Summary: - degrade if no mock installed Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/9854114f5788/ Changeset: 9854114f5788 Branch: None User: zzzeek Date: 2015-03-08 15:34:14+00:00 Summary: foo Affected #: 9 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4ba715f80a00/ Changeset: 4ba715f80a00 Branch: None User: zzzeek Date: 2015-03-08 16:33:38+00:00 Summary: - rename _select_wraps - replace force_result_map with a mini-API for nested result sets, add coverage 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...> - 2015-03-08 04:10:23
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/17b2fd3fba8e/ Changeset: 17b2fd3fba8e Branch: None User: zzzeek Date: 2015-03-08 04:03:27+00:00 Summary: - the change for #918 was of course not nearly that simple. The "wrapping" employed by the mssql and oracle dialects using the "iswrapper" argument was not being used intelligently by the compiler, and the result map was being written incorrectly, using *more* columns in the result map than were actually returned by the statement, due to "row number" columns that are inside the subquery. The compiler now writes out result map on the "top level" select in all cases fully, and for the mssql/oracle wrapping case extracts out the "proxied" columns in a second step, which only includes those columns that are proxied outwards to the top level. This change might have implications for 3rd party dialects that might be imitating oracle's approach. They can safely continue to use the "iswrapper" kw which is now ignored, but they may need to also add the _select_wraps argument as well. 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...> - 2015-03-07 23:28:32
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d70cf329cfff/ Changeset: d70cf329cfff Branch: None User: zzzeek Date: 2015-03-07 23:04:49+00:00 Summary: - do a full rewrite of callcounts 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...> - 2015-03-07 22:19:37
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b3d3795de0d4/ Changeset: b3d3795de0d4 Branch: positional_targeting User: zzzeek Date: 2015-03-07 22:18:31+00:00 Summary: - The SQL compiler now generates the mapping of expected columns such that they are matched to the received result set positionally, rather than by name. Originally, this was seen as a way to handle cases where we had columns returned with difficult-to-predict names, though in modern use that issue has been overcome by anonymous labeling. In this version, the approach basically reduces function call count per-result by a few dozen calls, or more for larger sets of result columns. The approach still degrades into a modern version of the old approach if textual elements modify the result map, or if any discrepancy in size exists between the compiled set of columns versus what was received, so there's no issue for partially or fully textual compilation scenarios where these lists might not line up. fixes #918 - callcounts still need to be adjusted down for this so zoomark tests won't pass at the moment 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...> - 2015-03-06 16:22:21
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/79025e272085/ Changeset: 79025e272085 Branch: rel_0_9 User: jocmeh Date: 2015-03-06 16:22:04+00:00 Summary: minor docstring fix in MappedCollection class (cherry picked from commit 34cb52e8d9f9bf345904315f16fb87ca9310d9cb) 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...> - 2015-03-06 16:20:58
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/34cb52e8d9f9/ Changeset: 34cb52e8d9f9 Branch: None User: jocmeh Date: 2015-03-06 15:58:30+00:00 Summary: minor docstring fix in MappedCollection class Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/0a1f720355f0/ Changeset: 0a1f720355f0 Branch: master User: zzzeek Date: 2015-03-06 16:20:45+00:00 Summary: Merged in jocmeh/sqlalchemy (pull request #46) minor docstring fix in MappedCollection class 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...> - 2015-03-03 00:28:21
|
6 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8038cfa0771f/ Changeset: 8038cfa0771f Branch: None User: tlocke Date: 2014-12-16 20:55:55+00:00 Summary: pg8000 client_encoding in create_engine() The pg8000 dialect now supports the setting of the PostgreSQL parameter client_encoding from create_engine(). Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c93706fa3319/ Changeset: c93706fa3319 Branch: None User: tlocke Date: 2014-12-16 21:03:04+00:00 Summary: Make pg8000 version detection more robust pg8000 uses Versioneer, which means that development versions have version strings that don't fit into the dotted triple number format. Released versions will always fit the triple format though. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/17e03a0ea86c/ Changeset: 17e03a0ea86c Branch: None User: tlocke Date: 2015-01-03 16:59:17+00:00 Summary: Changed pg8000 dialect to cope with native JSON For versions > 1.10.1 pg8000 returns de-serialized JSON objects rather than a string. SQL parameters are still strings though. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d140983148f1/ Changeset: d140983148f1 Branch: None User: zzzeek Date: 2015-03-03 00:00:19+00:00 Summary: Merge remote-tracking branch 'origin/pr/132' into pr132 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/cfb2eee0f3a1/ Changeset: cfb2eee0f3a1 Branch: None User: zzzeek Date: 2015-03-03 00:16:37+00:00 Summary: - add a skip for JSONB on pg8000 if we are on 1.10.1 or earlier Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/05ac6bcc0e2f/ Changeset: 05ac6bcc0e2f Branch: None User: zzzeek Date: 2015-03-03 00:27:21+00:00 Summary: - changelog and migration notes for new pg8000 features from pullreq github:132 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...> - 2015-03-02 16:31:42
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/cc58a605d6cd/ Changeset: cc58a605d6cd Branch: ticket_3054 User: zzzeek Date: 2015-03-02 16:30:55+00:00 Summary: - use the func_code itself for the hash key - py3k fixes 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...> - 2015-03-02 00:35:10
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4149ad4bc33f/ Changeset: 4149ad4bc33f Branch: None User: zzzeek Date: 2015-03-02 00:32:35+00:00 Summary: - add some deferreds Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f9e8549e1d80/ Changeset: f9e8549e1d80 Branch: ticket_3054 User: zzzeek Date: 2015-03-02 00:33:25+00:00 Summary: Merge branch 'master' into ticket_3054 Affected #: 43 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...> - 2015-03-01 21:14:33
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/79cbd377a62d/ Changeset: 79cbd377a62d Branch: master User: zzzeek Date: 2015-03-01 21:09:11+00:00 Summary: - squash-merge the final row_proc integration branch. this is a much more modest outcome than what we started with. The work of create_row_processor() for ColumnProperty objects is essentially done at query setup time combined with some lookups in _instance_processor(). - to allow this change for deferred columns, deferred columns no longer search for themselves in the result. If they've been set up as deferred without any explicit directive to undefer them, then this is what was asked for. if we don't do this, then we're stuck with this performance penalty for all deferred columns which in the vast majority of typical use cases (e.g. loading large, legacy tables or tables with many/large very seldom used values) won't be present in the result and won't be accessed at all. Affected #: 11 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...> - 2015-03-01 21:00:14
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7c568bb4e887/ Changeset: 7c568bb4e887 Branch: row_proc_integration_3 User: zzzeek Date: 2015-03-01 20:58:29+00:00 Summary: - turn on population fully. the change we have to make here is to no longer attempt to locate deferred columns in the result. if a column is desired as undeferred, it needs to be stated as such. 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...> - 2015-03-01 20:43:54
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/244bdae43fe7/ Changeset: 244bdae43fe7 Branch: None User: zzzeek Date: 2015-03-01 16:59:41+00:00 Summary: - factor setup into a function Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0bda660d92d8/ Changeset: 0bda660d92d8 Branch: None User: zzzeek Date: 2015-03-01 19:41:42+00:00 Summary: - inlining is commented out but overall structures are in place w 100% tests passing Affected #: 7 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4ea92df5ee4d/ Changeset: 4ea92df5ee4d Branch: row_proc_integration_3 User: zzzeek Date: 2015-03-01 20:42:11+00:00 Summary: - turn on population fully. the change we have to make here is to no longer attempt to locate deferred columns in the result. if a column is desired as undeferred, it needs to be stated as such. 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...> - 2015-03-01 02:19:17
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9cddb2afa200/ Changeset: 9cddb2afa200 Branch: row_proc_integration_2 User: zzzeek Date: 2015-03-01 02:16:34+00:00 Summary: - sort of working, not saving on much, eager loading of course totally broken. 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...> - 2015-03-01 00:30:48
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/149bcd108d9a/ Changeset: 149bcd108d9a Branch: None User: zzzeek Date: 2015-02-28 23:51:39+00:00 Summary: - OK this version not working for polymorphic or bundles yet, but for large loads it ties master, for many short loads it is slightly faster. if the code can be made clearer then it's a win Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/43289c861341/ Changeset: 43289c861341 Branch: row_proc_integration_2 User: zzzeek Date: 2015-03-01 00:04:40+00:00 Summary: - this adds polymorphic 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...> - 2015-02-28 20:27:17
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0a629e732979/ Changeset: 0a629e732979 Branch: row_proc_integration_2 User: zzzeek Date: 2015-02-28 20:26:01+00:00 Summary: - wrong! I didn't have the cprocs on the master test. we are barely slower. we do save on single queries, however. - but...wrong! we still can't do this approach for eager loads. we don't have context.outer_adapter available when we set up "quick" here, so this can't 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...> - 2015-02-28 19:59:47
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c2cdd32f8ba0/ Changeset: c2cdd32f8ba0 Branch: row_proc_integration_2 User: zzzeek Date: 2015-02-28 19:59:17+00:00 Summary: - BANG! saves 100K calls on orm2010!! woop 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...> - 2015-02-28 18:43:27
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c81a8143535c/ Changeset: c81a8143535c Branch: None User: zzzeek Date: 2015-02-28 18:30:22+00:00 Summary: - another approach. put row_processor back, don't do the thing with ad-hoc callables anymore, but at least make the path to row_processor being called more local to loading.py Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0a32227f3ac1/ Changeset: 0a32227f3ac1 Branch: row_proc_integration_2 User: zzzeek Date: 2015-02-28 18:42:58+00:00 Summary: - moving things around still 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...> - 2015-02-26 23:24:37
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/50fcf349fb0a/ Changeset: 50fcf349fb0a Branch: row_proc_integration User: zzzeek Date: 2015-02-26 23:18:48+00:00 Summary: - polymorphic loading, working very rudimentally running orm2010, the whole approach adds callcounts. code is more complex, less reliable, pretty much a total bust. will try to see if create_row_processor can remain but be called against either "result" or a context namespace ahead of time, and if this somehow can be used to simplify the need to call upon strategy lookup twice. 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. |
737 messages has been excluded from this view by a project administrator.
