Thread: [Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2013-05-25 21:14:52
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e9b29802ba99/ Changeset: e9b29802ba99 Branch: rel_0_9 User: zzzeek Date: 2013-05-25 23:04:35 Summary: Merge branch 'master' into rel_0_9 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/e14632ce136b/ Changeset: e14632ce136b Branch: rel_0_8 User: zzzeek Date: 2013-05-25 23:05:01 Summary: Merge branch 'master' into rel_0_8 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/900780bceaad/ Changeset: 900780bceaad Branch: rel_0_7 User: zzzeek Date: 2013-05-25 23:14:08 Summary: move to git dotfiles for 0.7 branch 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...> - 2013-05-26 21:00:39
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f939abe83034/ Changeset: f939abe83034 Branch: None User: zzzeek Date: 2013-05-26 22:32:55 Summary: mysql tests Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/b3654ee37abe/ Changeset: b3654ee37abe Branch: None User: zzzeek Date: 2013-05-26 22:39:50 Summary: postgresql tests Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4e930a7f780f/ Changeset: 4e930a7f780f Branch: rel_0_9 User: zzzeek Date: 2013-05-26 22:58:37 Summary: - add a test specific to sqlite testing cursor.description encoding (should probably be one in test_query or test_unicode...) - fix up test_unitofwork 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...> - 2013-05-26 21:19:19
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e2b8c893ca98/ Changeset: e2b8c893ca98 Branch: master User: zzzeek Date: 2013-05-26 23:18:04 Summary: fix this test Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/ff96d23a906d/ Changeset: ff96d23a906d Branch: rel_0_8 User: zzzeek Date: 2013-05-26 23:18:17 Summary: Merge branch 'master' into rel_0_8 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/2ddcd20267c8/ Changeset: 2ddcd20267c8 Branch: rel_0_9 User: zzzeek Date: 2013-05-26 23:18:27 Summary: Merge branch 'master' into rel_0_9 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...> - 2013-05-26 21:58:41
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/46b0b14fde37/ Changeset: 46b0b14fde37 Branch: None User: zzzeek Date: 2013-05-26 23:37:03 Summary: cleanup for oracle Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/abc433129384/ Changeset: abc433129384 Branch: None User: zzzeek Date: 2013-05-26 23:39:53 Summary: a few more oracle fixes Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/38f65baf1895/ Changeset: 38f65baf1895 Branch: rel_0_9 User: zzzeek Date: 2013-05-26 23:58:07 Summary: - oracle tests passing in py3k!! 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...> - 2013-05-28 05:23:25
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/94096593ca92/ Changeset: 94096593ca92 Branch: master User: zzzeek Date: 2013-05-28 07:22:10 Summary: Fixed a small bug in the dogpile example where the generation of SQL cache keys wasn't applying deduping labels to the statement the same way :class:`.Query` normally does. Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a5bacf91f0c8/ Changeset: a5bacf91f0c8 Branch: rel_0_8 User: zzzeek Date: 2013-05-28 07:22:23 Summary: Merge branch 'master' into rel_0_8 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/9fc6201f0c03/ Changeset: 9fc6201f0c03 Branch: rel_0_9 User: zzzeek Date: 2013-05-28 07:22:32 Summary: Merge branch 'master' into rel_0_9 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...> - 2013-05-30 20:00:41
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/1e46612d3f2e/ Changeset: 1e46612d3f2e Branch: rel_0_9 User: zzzeek Date: 2013-05-30 01:57:40 Summary: re-add these... Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/c4c37c0201a9/ Changeset: c4c37c0201a9 Branch: None User: zzzeek Date: 2013-05-30 21:56:00 Summary: - the distinct hash code logic here is entirely obsolete as you can do eq_() on columnelements now with a meaningful bool; jython is entirely a non-starter right now in any case as 2.7 doesn't support common accessors like __defaults__ Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/5eab95b8e19a/ Changeset: 5eab95b8e19a Branch: master User: zzzeek Date: 2013-05-30 21:59:24 Summary: Merge branch 'rel_0_9' (was already merged...git wants to merge again) Affected #: 0 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...> - 2013-05-31 00:27:26
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/04317bd5a887/ Changeset: 04317bd5a887 Branch: None User: zzzeek Date: 2013-05-31 02:09:44 Summary: The "auto-aliasing" behavior of the :class:`.Query.select_from` method has been turned off. The specific behavior is now availble via a new method :class:`.Query.select_entity_from`. [ticket:2736] Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/489312998f2f/ Changeset: 489312998f2f Branch: rel_0_8 User: zzzeek Date: 2013-05-31 02:24:48 Summary: Added a new method :meth:`.Query.select_entity_from` which will in 0.9 replace part of the functionality of :meth:`.Query.select_from`. In 0.8, the two methods perform the same function, so that code can be migrated to use the :meth:`.Query.select_entity_from` method as appropriate. See the 0.9 migration guide for details. [ticket:2736] Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/1cc6494802b1/ Changeset: 1cc6494802b1 Branch: master User: zzzeek Date: 2013-05-31 02:26:45 Summary: add a test for the exception we want to raise 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...> - 2013-06-03 17:55:11
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/74c98bf182a1/ Changeset: 74c98bf182a1 Branch: None User: zzzeek Date: 2013-06-03 19:13:16 Summary: Merge branch 'master' into ticket_1068 Affected #: 219 files https://bitbucket.org/zzzeek/sqlalchemy/commits/f2328d6df4dc/ Changeset: f2328d6df4dc Branch: ticket_1068 User: zzzeek Date: 2013-06-03 19:45:28 Summary: test tweak Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/82c11cc94b41/ Changeset: 82c11cc94b41 Branch: master User: zzzeek Date: 2013-06-03 19:53:42 Summary: - fdb is now official, [ticket:2504] - restore the rollback cleanup handler, pg8000 is mostly obsolete as a dialect and the firebird drivers need it 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...> - 2013-06-08 23:01:24
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c6615b41a6d9/ Changeset: c6615b41a6d9 Branch: None User: zzzeek Date: 2013-06-08 22:14:09 Summary: formatting Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/31063d16f209/ Changeset: 31063d16f209 Branch: None User: zzzeek Date: 2013-06-09 00:41:59 Summary: - tests for the alias() API - docs docs docs Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/85368d25ed15/ Changeset: 85368d25ed15 Branch: master User: zzzeek Date: 2013-06-09 00:54:14 Summary: get nested joins to render on oracle 8 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...> - 2013-06-09 21:55:29
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c69fe4acf892/ Changeset: c69fe4acf892 Branch: None User: malor Date: 2013-06-09 22:49:55 Summary: Add basic support of unique constraints reflection Inspection API already supports reflection of table indexes information and those also include unique constraints (at least for PostgreSQL and MySQL). But it could be actually useful to distinguish between indexes and plain unique constraints (though both are implemented in the same way internally in RDBMS). This change adds a new method to Inspection API - get_unique_constraints() and implements it for SQLite, PostgreSQL and MySQL dialects. Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/decf47a770b2/ Changeset: decf47a770b2 Branch: None User: zzzeek Date: 2013-06-09 23:39:30 Summary: Merge pull request #4 from malor/reflect_constraints Add basic support of unique constraints reflection Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/258d2a8315a1/ Changeset: 258d2a8315a1 Branch: master User: zzzeek Date: 2013-06-09 23:54:11 Summary: - get_unique_constraints() pull request - version (0.9 for now) - changelog - move the test into the test suite so that all dialects can take advantage of it 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...> - 2013-06-15 19:30:00
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b92007da7d9c/ Changeset: b92007da7d9c Branch: master User: zzzeek Date: 2013-06-15 21:20:48 Summary: Fixed bug in polymorphic SQL generation where multiple joined-inheritance entities against the same base class joined to each other as well would not track columns on the base table independently of each other if the string of joins were more than two entities long. Also in 0.8.2. [ticket:2759] Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/aee826890c75/ Changeset: aee826890c75 Branch: None User: zzzeek Date: 2013-06-15 21:29:00 Summary: Fixed bug in polymorphic SQL generation where multiple joined-inheritance entities against the same base class joined to each other as well would not track columns on the base table independently of each other if the string of joins were more than two entities long. Also in 0.8.2. [ticket:2759] Conflicts: doc/build/changelog/changelog_09.rst Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/abd17f4daffd/ Changeset: abd17f4daffd Branch: rel_0_8 User: zzzeek Date: 2013-06-15 21:29:21 Summary: fix tests here for 0.8 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...> - 2013-06-23 19:13:54
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d4bbfe63d643/ Changeset: d4bbfe63d643 Branch: None User: zzzeek Date: 2013-06-23 20:12:21 Summary: support for type propagation when column is sent Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/63231464be7c/ Changeset: 63231464be7c Branch: None User: zzzeek Date: 2013-06-23 20:42:27 Summary: - fine grained checks for various conditions Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/e3e8af477851/ Changeset: e3e8af477851 Branch: ticket_1765 User: zzzeek Date: 2013-06-23 21:13:26 Summary: - more bookkeeping involving removal of tables... 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...> - 2013-06-25 22:06:47
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/89f9374c544b/ Changeset: 89f9374c544b Branch: None User: zzzeek Date: 2013-06-25 23:32:51 Summary: - rework of correlation, continuing on #2668, #2746 - add new flag "froms=True" to correlate(), correlate_except(); means a correlation should occur outwards even if this clause is in the FROM clause of another SELECT - add support for correlations to propagate all the way in; because correlations require context now, need to make sure a select enclosure of any level takes effect any number of levels deep. - fix what we said correlate_except() was supposed to do when we first released #2668 - "the FROM clause is left intact if the correlated SELECT is not used in the context of an enclosing SELECT..." - it was not considering the "existing_froms" collection at all, and prohibited additional FROMs from being placed in an any() or has(). Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/98f2e371d272/ Changeset: 98f2e371d272 Branch: None User: zzzeek Date: 2013-06-25 23:52:27 Summary: add test for multilevel any() Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/480ee4f6ed00/ Changeset: 480ee4f6ed00 Branch: ticket_2746 User: zzzeek Date: 2013-06-26 00:05:04 Summary: fix cloned_difference and test both 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...> - 2013-06-26 17:34:23
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f76cae4bc92d/ Changeset: f76cae4bc92d Branch: None User: zzzeek Date: 2013-06-26 19:19:45 Summary: - rework of correlation, continuing on #2668, #2746 - add support for correlations to propagate all the way in; because correlations require context now, need to make sure a select enclosure of any level takes effect any number of levels deep. - fix what we said correlate_except() was supposed to do when we first released #2668 - "the FROM clause is left intact if the correlated SELECT is not used in the context of an enclosing SELECT..." - it was not considering the "existing_froms" collection at all, and prohibited additional FROMs from being placed in an any() or has(). - add test for multilevel any() - lots of docs, including glossary entries as we really need to define "WHERE clause", "columns clause" etc. so that we can explain correlation better - based on the insight that a SELECT can correlate anything that ultimately came from an enclosing SELECT that links to this one via WHERE/columns/HAVING/ORDER BY, have the compiler keep track of the FROM lists that correspond in this way, link it to the asfrom flag, so that we send to _get_display_froms() the exact list of candidate FROMs to correlate. no longer need any asfrom logic in the Select() itself - preserve 0.8.1's behavior for correlation when no correlate options are given, not to mention 0.7 and prior's behavior of not propagating implicit correlation more than one level.. this is to reduce surprises/hard-to-debug situations when a user isn't trying to correlate anything. Affected #: 10 files https://bitbucket.org/zzzeek/sqlalchemy/commits/f76e65727d66/ Changeset: f76e65727d66 Branch: master User: zzzeek Date: 2013-06-26 19:24:07 Summary: Merge branch 'ticket_2746' Conflicts: doc/build/changelog/changelog_08.rst doc/build/changelog/changelog_09.rst Affected #: 10 files https://bitbucket.org/zzzeek/sqlalchemy/commits/b4697e9e1875/ Changeset: b4697e9e1875 Branch: rel_0_8 User: zzzeek Date: 2013-06-26 19:32:39 Summary: - rework of correlation, continuing on #2668, #2746 - add support for correlations to propagate all the way in; because correlations require context now, need to make sure a select enclosure of any level takes effect any number of levels deep. - fix what we said correlate_except() was supposed to do when we first released #2668 - "the FROM clause is left intact if the correlated SELECT is not used in the context of an enclosing SELECT..." - it was not considering the "existing_froms" collection at all, and prohibited additional FROMs from being placed in an any() or has(). - add test for multilevel any() - lots of docs, including glossary entries as we really need to define "WHERE clause", "columns clause" etc. so that we can explain correlation better - based on the insight that a SELECT can correlate anything that ultimately came from an enclosing SELECT that links to this one via WHERE/columns/HAVING/ORDER BY, have the compiler keep track of the FROM lists that correspond in this way, link it to the asfrom flag, so that we send to _get_display_froms() the exact list of candidate FROMs to correlate. no longer need any asfrom logic in the Select() itself - preserve 0.8.1's behavior for correlation when no correlate options are given, not to mention 0.7 and prior's behavior of not propagating implicit correlation more than one level.. this is to reduce surprises/hard-to-debug situations when a user isn't trying to correlate anything. Conflicts: doc/build/changelog/changelog_08.rst doc/build/changelog/changelog_09.rst lib/sqlalchemy/sql/compiler.py Affected #: 9 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |
From: Bitbucket <com...@bi...> - 2013-07-02 16:17:55
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7d3fcc1c2e09/ Changeset: 7d3fcc1c2e09 Branch: None User: zzzeek Date: 2013-07-02 17:44:33 Summary: - use correct attribute - catch this error more effectively Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/68cfe57a10da/ Changeset: 68cfe57a10da Branch: None User: zzzeek Date: 2013-07-02 17:52:49 Summary: profile updates. a few extra method calls but the code is better organized Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/e93b40e91d0b/ Changeset: e93b40e91d0b Branch: ticket_2770 User: zzzeek Date: 2013-07-02 18:17:20 Summary: - more profiles... 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...> - 2013-07-05 00:04:12
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3f75c6aff6e8/ Changeset: 3f75c6aff6e8 Branch: rel_0_8 User: zzzeek Date: 2013-07-05 02:01:55 Summary: Fixed bug whereby attribute history functions would fail when an object we moved from "persistent" to "pending" using the :func:`.make_transient` function, for operations involving collection-based backrefs. [ticket:2773] Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/806f5a418368/ Changeset: 806f5a418368 Branch: None User: zzzeek Date: 2013-07-05 02:02:31 Summary: Fixed bug whereby attribute history functions would fail when an object we moved from "persistent" to "pending" using the :func:`.make_transient` function, for operations involving collection-based backrefs. [ticket:2773] Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/29ce6db26dea/ Changeset: 29ce6db26dea Branch: master User: zzzeek Date: 2013-07-05 02:03:18 Summary: 0.9 changelog 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...> - 2013-07-08 04:43:55
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ff58435d49a8/ Changeset: ff58435d49a8 Branch: None User: zzzeek Date: 2013-07-07 22:17:46 Summary: explicit better than implicit so use "named=True" for kw thing Affected #: 7 files https://bitbucket.org/zzzeek/sqlalchemy/commits/1fb4d6e3f5eb/ Changeset: 1fb4d6e3f5eb Branch: None User: zzzeek Date: 2013-07-07 22:28:34 Summary: add support for "complex" conversion where we have fewer args in the new signature Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/9bdfb59cedd9/ Changeset: 9bdfb59cedd9 Branch: ticket_2775 User: zzzeek Date: 2013-07-07 23:05:43 Summary: bulk update/delete methods 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...> - 2013-07-17 15:26:27
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0a54a4a4b089/ Changeset: 0a54a4a4b089 Branch: master User: zzzeek Date: 2013-07-17 17:18:59 Summary: Fixed bug in :class:`.CheckConstraint` DDL where the "quote" flag from a :class:`.Column` object would not be propagated. Also in 0.8.3, 0.7.11. [ticket:2784] Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/436ba1601d33/ Changeset: 436ba1601d33 Branch: rel_0_8 User: zzzeek Date: 2013-07-17 17:19:50 Summary: Fixed bug in :class:`.CheckConstraint` DDL where the "quote" flag from a :class:`.Column` object would not be propagated. Also in 0.8.3, 0.7.11. [ticket:2784] Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6f265a4e6555/ Changeset: 6f265a4e6555 Branch: rel_0_7 User: zzzeek Date: 2013-07-17 17:22:42 Summary: Fixed bug in :class:`.CheckConstraint` DDL where the "quote" flag from a :class:`.Column` object would not be propagated. Also in 0.8.3, 0.7.11. [ticket:2784] 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...> - 2013-07-23 01:13:08
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4134af421fd5/ Changeset: 4134af421fd5 Branch: None User: zzzeek Date: 2013-07-23 00:37:35 Summary: registration... Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/301125e05e1b/ Changeset: 301125e05e1b Branch: None User: zzzeek Date: 2013-07-23 01:38:55 Summary: so this is pretty much working, and weakref cleanup seems to work too, but the memusage tests are failing all over the place, so I guess it doesn't really work. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/47385fec88d1/ Changeset: 47385fec88d1 Branch: ticket_2268 User: zzzeek Date: 2013-07-23 03:12:22 Summary: OK this passes everything, still some scary warnings I'd like to figure out, and overall this is definitely more complicated than I'd prefer 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...> - 2013-07-25 23:22:28
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b22463d59a33/ Changeset: b22463d59a33 Branch: None User: zzzeek Date: 2013-07-23 18:22:28 Summary: py3k fix Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8db7a4d518c8/ Changeset: 8db7a4d518c8 Branch: None User: zzzeek Date: 2013-07-26 01:18:15 Summary: use the correct listener fn here Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a9932a8b6d02/ Changeset: a9932a8b6d02 Branch: ticket_2268 User: zzzeek Date: 2013-07-26 01:22:02 Summary: inline this 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...> - 2013-07-31 23:09:37
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c6fdfeed00e2/ Changeset: c6fdfeed00e2 Branch: None User: zzzeek Date: 2013-08-01 01:05:58 Summary: - update ORM event docs to include that you can listen on an unmapped base, [ticket:2777] Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/5d4094ba739b/ Changeset: 5d4094ba739b Branch: master User: zzzeek Date: 2013-08-01 01:07:13 Summary: fix missing comma Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/312764983b90/ Changeset: 312764983b90 Branch: rel_0_8 User: zzzeek Date: 2013-08-01 01:08:05 Summary: - update ORM event docs to include that you can listen on an unmapped base, [ticket:2777] Conflicts: lib/sqlalchemy/orm/events.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...> - 2013-08-01 01:08:50
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/25839c064d99/ Changeset: 25839c064d99 Branch: master User: zzzeek Date: 2013-08-01 03:05:33 Summary: Updates to MySQL reserved words for versions 5.5, 5.6, courtesy Hanno Schlichting. Also in 0.8.3, 0.7.11. [ticket:2791] Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/8aa563110728/ Changeset: 8aa563110728 Branch: rel_0_8 User: zzzeek Date: 2013-08-01 03:06:21 Summary: Updates to MySQL reserved words for versions 5.5, 5.6, courtesy Hanno Schlichting. Also in 0.8.3, 0.7.11. [ticket:2791] Conflicts: doc/build/changelog/changelog_09.rst Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d28d9f2bc85a/ Changeset: d28d9f2bc85a Branch: rel_0_7 User: zzzeek Date: 2013-08-01 03:07:19 Summary: Updates to MySQL reserved words for versions 5.5, 5.6, courtesy Hanno Schlichting. Also in 0.8.3, 0.7.11. [ticket:2791] 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...> - 2013-08-08 20:41:17
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0f68eceff467/ Changeset: 0f68eceff467 Branch: None User: Severin Orth Date: 2013-08-08 02:09:42 Summary: Typo Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9dcdf7ff735b/ Changeset: 9dcdf7ff735b Branch: master User: zzzeek Date: 2013-08-08 22:39:23 Summary: Merge pull request #21 from svrin/patch-1 Typo in engines.rst Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/ca078368ca66/ Changeset: ca078368ca66 Branch: rel_0_8 User: zzzeek Date: 2013-08-08 22:40:47 Summary: Merge pull request #21 from svrin/patch-1 Typo in engines.rst 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...> - 2013-08-18 19:41:36
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/676876f46685/ Changeset: 676876f46685 Branch: master User: zzzeek Date: 2013-08-18 21:34:23 Summary: Fixed a potential issue in an ordered sequence implementation used by the ORM to iterate mapper hierarchies; under the Jython interpreter this implementation wasn't ordered, even though cPython and Pypy maintained ordering. Also in 0.8.3. [ticket:2794] Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4b1ca2302749/ Changeset: 4b1ca2302749 Branch: None User: zzzeek Date: 2013-08-18 21:35:23 Summary: Fixed a potential issue in an ordered sequence implementation used by the ORM to iterate mapper hierarchies; under the Jython interpreter this implementation wasn't ordered, even though cPython and Pypy maintained ordering. Also in 0.8.3. [ticket:2794] Conflicts: doc/build/changelog/changelog_09.rst lib/sqlalchemy/util/_collections.py Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/17274222f1bd/ Changeset: 17274222f1bd Branch: rel_0_8 User: zzzeek Date: 2013-08-18 21:36:26 Summary: fix the merge 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...> - 2013-08-18 20:12:21
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/01aeeb96f923/ Changeset: 01aeeb96f923 Branch: None User: zzzeek Date: 2013-08-18 22:10:23 Summary: - use newly fixed WeakSequence (#2794) to not have to rely on class name for sorting in #2779 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/22cd5c5cd588/ Changeset: 22cd5c5cd588 Branch: rel_0_8 User: zzzeek Date: 2013-08-18 22:10:46 Summary: changelog adjust... Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/806a9b778506/ Changeset: 806a9b778506 Branch: master User: zzzeek Date: 2013-08-18 22:11:15 Summary: 0.9 needs 0.8's changelog 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. |