sqlalchemy-commits Mailing List for SQLAlchemy (Page 75)
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-04 00:14:05
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b069127b2d3f/ Changeset: b069127b2d3f Branch: None User: zzzeek Date: 2014-02-04 01:13:16 Summary: - Improved the initialization logic of composite attributes such that calling ``MyClass.attribute`` will not require that the configure mappers step has occurred, e.g. it will just work without throwing any error. [ticket:2935] 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-03 17:13:44
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/69a66d58c2d7/ Changeset: 69a66d58c2d7 Branch: None User: zzzeek Date: 2014-02-03 18:13:17 Summary: 0.9.3 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-03 17:12:19
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8b08b1a35b85/ Changeset: 8b08b1a35b85 Branch: None User: zzzeek Date: 2014-02-03 18:04:51 Summary: - Fixed bug which prevented MySQLdb-based dialects (e.g. pymysql) from working in Py3K, where a check for "connection charset" would fail due to Py3K's more strict value comparison rules. The call in question wasn't taking the database version into account in any case as the server version was still None at that point, so the method overall has been simplified to rely upon connection.character_set_name(). [ticket:2933] Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/cd1baf6572ba/ Changeset: cd1baf6572ba Branch: None User: zzzeek Date: 2014-02-03 18:06:57 Summary: - Fixed bug which prevented MySQLdb-based dialects (e.g. pymysql) from working in Py3K, where a check for "connection charset" would fail due to Py3K's more strict value comparison rules. The call in question wasn't taking the database version into account in any case as the server version was still None at that point, so the method overall has been simplified to rely upon connection.character_set_name(). [ticket:2933] Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7a9e8b2312bb/ Changeset: 7a9e8b2312bb Branch: None User: zzzeek Date: 2014-02-03 18:11:23 Summary: - this seems to be the best string for pymysql Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/b77f958b8b15/ Changeset: b77f958b8b15 Branch: rel_0_8 User: zzzeek Date: 2014-02-03 18:11:44 Summary: - this seems to be the best string for pymysql 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-03 00:42:11
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/064df1d1ee64/ Changeset: 064df1d1ee64 Branch: None User: zzzeek Date: 2014-02-03 01:19:24 Summary: 0.9.2 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/37d1f8983ce4/ Changeset: 37d1f8983ce4 Branch: None User: zzzeek Date: 2014-02-03 01:28:41 Summary: 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-03 00:06:16
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b85f0b568127/ Changeset: b85f0b568127 Branch: None User: zzzeek Date: 2014-02-03 01:05:36 Summary: - Added a tweak to the "history_meta" example where the check for "history" on a relationship-bound attribute will now no longer emit any SQL if the relationship is unloaded. 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-02 23:23:04
|
16 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/601dcadb2cf8/ Changeset: 601dcadb2cf8 Branch: None User: nakagami Date: 2013-07-13 07:37:36 Summary: @testing.crashes('mysql+cymysql', 'blocking') Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/1e811be25912/ Changeset: 1e811be25912 Branch: None User: nakagami Date: 2013-07-13 08:46:16 Summary: mysql+cython supports_sane_rowcount = True Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/34ae0bb793b1/ Changeset: 34ae0bb793b1 Branch: None User: nakagami Date: 2013-07-13 12:27:23 Summary: remove skip decorator for mysql+cymysql Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/657636c9aec3/ Changeset: 657636c9aec3 Branch: None User: nakagami Date: 2013-07-14 01:46:47 Summary: not supports_sane_multi_rowcount in cymysql Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/cae797501cc8/ Changeset: cae797501cc8 Branch: None User: nakagami Date: 2013-07-14 02:10:49 Summary: use map() instead of util.iterbytes() Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/e06f02e2aa32/ Changeset: e06f02e2aa32 Branch: None User: nakagami Date: 2013-07-14 02:36:31 Summary: not fails_if cymysql Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/64cfe71cfcd7/ Changeset: 64cfe71cfcd7 Branch: None User: nakagami Date: 2013-07-14 03:34:52 Summary: fix compat.iterbytes import Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0c287e64f7b3/ Changeset: 0c287e64f7b3 Branch: None User: nakagami Date: 2013-07-16 07:26:52 Summary: set cymysql's supports_unicode_statements=True for python3 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9519dc9bd30b/ Changeset: 9519dc9bd30b Branch: None User: nakagami Date: 2013-08-18 01:34:42 Summary: Merge branch 'master' into cymysql Affected #: 125 files https://bitbucket.org/zzzeek/sqlalchemy/commits/575eaf8b239f/ Changeset: 575eaf8b239f Branch: None User: nakagami Date: 2013-10-27 10:33:46 Summary: Merge branch 'master' into cymysql Affected #: 187 files https://bitbucket.org/zzzeek/sqlalchemy/commits/9ae000a03d9b/ Changeset: 9ae000a03d9b Branch: None User: nakagami Date: 2014-01-24 10:20:01 Summary: Merge branch 'master' into cymysql Conflicts: lib/sqlalchemy/util/__init__.py Affected #: 409 files https://bitbucket.org/zzzeek/sqlalchemy/commits/f78bf49be12f/ Changeset: f78bf49be12f Branch: None User: nakagami Date: 2014-01-24 10:20:32 Summary: Merge branch 'cymysql' of github.com:nakagami/sqlalchemy into cymysql Affected #: 0 files https://bitbucket.org/zzzeek/sqlalchemy/commits/b2094fd832ce/ Changeset: b2094fd832ce Branch: None User: nakagami Date: 2014-01-25 06:18:37 Summary: fix mysql+cymysql dialect Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/6b1cc6849179/ Changeset: 6b1cc6849179 Branch: t User: zzzeek Date: 2014-02-03 00:15:38 Summary: Merge branch 'cymysql' of github.com:nakagami/sqlalchemy into t Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/1b8a49576786/ Changeset: 1b8a49576786 Branch: None User: zzzeek Date: 2014-02-03 00:20:16 Summary: - add a few missing methods to the cymysql dialect Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/2ac2bbd35088/ Changeset: 2ac2bbd35088 Branch: rel_0_8 User: zzzeek Date: 2014-02-03 00:21:09 Summary: - add a few missing methods to the cymysql dialect 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-02 23:02:42
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4b3967087565/ Changeset: 4b3967087565 Branch: None User: zzzeek Date: 2014-02-03 00:01:59 Summary: - lets intersphinx the new alembic article on constraint names 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-02 21:34:59
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0326f3cf014f/ Changeset: 0326f3cf014f Branch: None User: zzzeek Date: 2014-02-02 22:33:54 Summary: - Added :paramref:`.MetaData.reflect.**dialect_kwargs` to support dialect-level reflection options for all :class:`.Table` objects reflected. - Added a new dialect-level argument ``postgresql_ignore_search_path``; this argument is accepted by both the :class:`.Table` constructor as well as by the :meth:`.MetaData.reflect` method. When in use against Postgresql, a foreign-key referenced table which specifies a remote schema name will retain that schema name even if the name is present in the ``search_path``; the default behavior since 0.7.3 has been that schemas present in ``search_path`` would not be copied to reflected :class:`.ForeignKey` objects. The documentation has been updated to describe in detail the behavior of the ``pg_get_constraintdef()`` function and how the ``postgresql_ignore_search_path`` feature essentially determines if we will honor the schema qualification reported by this function or not. [ticket:2922] 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-02 19:41:17
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2d4b457924fa/ Changeset: 2d4b457924fa Branch: None User: zzzeek Date: 2014-02-02 20:37:43 Summary: - The behavior of :meth:`.Table.tometadata` has been adjusted such that the schema target of a :class:`.ForeignKey` will not be changed unless that schema matches that of the parent table. That is, if a table "schema_a.user" has a foreign key to "schema_b.order.id", the "schema_b" target will be maintained whether or not the "schema" argument is passed to :meth:`.Table.tometadata`. However if a table "schema_a.user" refers to "schema_a.order.id", the presence of "schema_a" will be updated on both the parent and referred tables. This is a behavioral change hence isn't likely to be backported to 0.8; it is assumed that the previous behavior is pretty buggy however and that it's unlikely anyone was relying upon it. Additionally, a new parameter has been added :paramref:`.Table.tometadata.referred_schema_fn`. This refers to a callable function which will be used to determine the new referred schema for any :class:`.ForeignKeyConstraint` encountered in the tometadata operation. This callable can be used to revert to the previous behavior or to customize how referred schemas are treated on a per-constraint basis. [ticket:2913] - rework the tests in test.sql.test_metadata, all the "tometadata" tests now under new class ToMetaDataTest Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4ed4266803cb/ Changeset: 4ed4266803cb Branch: None User: zzzeek Date: 2014-02-02 20:40:23 Summary: - use from_statement() for the ORM column test - with select_from(), add external order by so that Oracle orders correctly 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-02 16:06:39
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/29de1077b35f/ Changeset: 29de1077b35f Branch: None User: zzzeek Date: 2014-02-02 17:06:08 Summary: - Fixed bug in new :class:`.TextAsFrom` construct where :class:`.Column`- oriented row lookups were not matching up to the ad-hoc :class:`.ColumnClause` objects that :class:`.TextAsFrom` generates, thereby making it not usable as a target in :meth:`.Query.from_statement`. Also fixed :meth:`.Query.from_statement` mechanics to not mistake a :class:`.TextAsFrom` for a :class:`.Select` construct. This bug is also an 0.9 regression as the :meth:`.Text.columns` method is called to accommodate the :paramref:`.text.typemap` argument. [ticket:2932] 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-01 23:22:05
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9a3219bdac9a/ Changeset: 9a3219bdac9a Branch: ticket_2923 User: zzzeek Date: 2014-02-02 00:20:16 Summary: - changelog - docs - support callables so that any token can be worked up Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/5b0919f3f5c7/ Changeset: 5b0919f3f5c7 Branch: None User: zzzeek Date: 2014-02-02 00:21:04 Summary: - Added a new feature which allows automated naming conventions to be applied to :class:`.Constraint` and :class:`.Index` objects. Based on a recipe in the wiki, the new feature uses schema-events to set up names as various schema objects are associated with each other. The events then expose a configuration system through a new argument :paramref:`.MetaData.naming_convention`. This system allows production of both simple and custom naming schemes for constraints and indexes on a per-:class:`.MetaData` basis. [ticket:2923] commit 7e65e52c086652de3dd3303c723f98f09af54db8 Author: Mike Bayer <mi...@zz...> Date: Sat Feb 1 15:09:04 2014 -0500 - first pass at new naming approach Affected #: 8 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-01 20:09:44
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7e65e52c0866/ Changeset: 7e65e52c0866 Branch: ticket_2923 User: zzzeek Date: 2014-02-01 21:09:04 Summary: - first pass at new naming approach 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-02-01 18:23:14
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/32a1db368599/ Changeset: 32a1db368599 Branch: None User: zzzeek Date: 2014-02-01 19:22:43 Summary: add a skip for oracle on this 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-01 04:17:55
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b8178a0bba35/ Changeset: b8178a0bba35 Branch: None User: zzzeek Date: 2014-02-01 05:13:13 Summary: - don't duplicate docs for Pool within QueuePool - add huge warning regarding how use_threadlocal probably not what you want Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/5f144b2e4354/ Changeset: 5f144b2e4354 Branch: rel_0_8 User: zzzeek Date: 2014-02-01 05:16:34 Summary: - don't duplicate docs for Pool within QueuePool - add huge warning regarding how use_threadlocal probably not what you want 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-01 00:58:37
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/33c7cfff6eb1/ Changeset: 33c7cfff6eb1 Branch: None User: zzzeek Date: 2014-02-01 01:57:38 Summary: - Added a new directive used within the scope of an attribute "set" operation to disable autoflush, in the case that the attribute needs to lazy-load the "old" value, as in when replacing one-to-one values or some kinds of many-to-one. A flush at this point otherwise occurs at the point that the attribute is None and can cause NULL violations. [ticket:2921] 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-01 00:14:45
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/6b3ecd14eae1/ Changeset: 6b3ecd14eae1 Branch: master User: zzzeek Date: 2014-02-01 01:14:08 Summary: - Added a new parameter :paramref:`.Operators.op.is_comparison`. This flag allows a custom op from :meth:`.Operators.op` to be considered as a "comparison" operator, thus usable for custom :paramref:`.relationship.primaryjoin` conditions. 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-01-31 22:58:03
|
7 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a1f8479215f8/ Changeset: a1f8479215f8 Branch: None User: witsch Date: 2014-01-31 17:33:44 Summary: expose `binary_type` in `util` module it is used in `sql/compiler.py(849)render_literal_value()` Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/5283b0cb3185/ Changeset: 5283b0cb3185 Branch: None User: zzzeek Date: 2014-01-31 23:27:35 Summary: - add a test for pullreq github:63 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/95c370cc65be/ Changeset: 95c370cc65be Branch: None User: zzzeek Date: 2014-01-31 23:27:55 Summary: Merge branch 'fix-convenience-import' of github.com:witsch/sqlalchemy into t Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/e7f906f5e667/ Changeset: e7f906f5e667 Branch: None User: zzzeek Date: 2014-01-31 23:29:19 Summary: no Binary here if we are running a test with no DBAPI Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/1cf18e5cbb62/ Changeset: 1cf18e5cbb62 Branch: None User: zzzeek Date: 2014-01-31 23:31:20 Summary: changelog Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/4b57df9e30b0/ Changeset: 4b57df9e30b0 Branch: None User: zzzeek Date: 2014-01-31 23:31:46 Summary: changelog Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/b360dbf7ebb7/ Changeset: b360dbf7ebb7 Branch: None User: zzzeek Date: 2014-01-31 23:57:17 Summary: - Fixed bug whereby SQLite compiler failed to propagate compiler arguments such as "literal binds" into a CAST expression. - Fixed bug whereby binary type would fail in some cases if used with a "test" dialect, such as a DefaultDialect or other dialect with no DBAPI. - Fixed bug where "literal binds" wouldn't work with a bound parameter that's a binary type. A similar, but different, issue is fixed in 0.8. 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-01-29 22:34:26
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/66fe0880bae3/ Changeset: 66fe0880bae3 Branch: rel_0_8 User: zzzeek Date: 2014-01-29 23:09:50 Summary: - add a test for [ticket:2927], which is an 0.9 issue but only because 0.8 isn't annotating correctly Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8afb69ced876/ Changeset: 8afb69ced876 Branch: None User: zzzeek Date: 2014-01-29 23:33:28 Summary: - Fixed regression whereby the "annotation" system used by the ORM was leaking into the names used by standard functions in :mod:`sqlalchemy.sql.functions`, such as ``func.coalesce()`` and ``func.max()``. Using these functions in ORM attributes and thus producing annotated versions of them could corrupt the actual function name rendered in the SQL. [ticket:2927] 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-01-29 19:57:43
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/00e78f5f76c0/ Changeset: 00e78f5f76c0 Branch: None User: zzzeek Date: 2014-01-29 20:57:18 Summary: - better way to do it 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-01-29 19:57:06
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7d56e4f135bd/ Changeset: 7d56e4f135bd Branch: None User: zzzeek Date: 2014-01-29 20:55:58 Summary: - add TypeError handling to the tests here, ensure TypeError for the control is a TypeError for the row, as is raised on py3k when less/greater operators are used on incompatible types 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-01-29 04:46:07
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d4c908ded1e9/ Changeset: d4c908ded1e9 Branch: None User: zzzeek Date: 2014-01-29 05:43:14 Summary: - Fixed 0.9 regression where the new sortable support for :class:`.RowProxy` would lead to ``TypeError`` when compared to non-tuple types as it attempted to apply tuple() to the "other" object unconditionally. The full range of Python comparison operators have now been implemented on :class:`.RowProxy`, using an approach that guarantees a comparison system that is equivalent to that of a tuple, and the "other" object is only coerced if it's an instance of RowProxy. [ticket:2924] 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-01-29 00:49:44
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b05adc9507cb/ Changeset: b05adc9507cb Branch: rel_0_8 User: zzzeek Date: 2014-01-29 01:49:15 Summary: - repair the fixture/test here to make sure state isn't left over causing other tests to fail 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-01-27 18:35:27
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/d8d03011b8da/ Changeset: d8d03011b8da Branch: None User: zzzeek Date: 2014-01-27 19:34:33 Summary: - repair the fixture/test here to make sure state isn't left over causing other tests to fail 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-01-27 01:02:40
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/da4256d3dc2f/ Changeset: da4256d3dc2f Branch: rel_0_8 User: zzzeek Date: 2014-01-27 02:01:57 Summary: docs Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/d20d7549fd32/ Changeset: d20d7549fd32 Branch: None User: zzzeek Date: 2014-01-27 02:02:08 Summary: - docs 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-01-26 06:05:25
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ae3f2abe06af/ Changeset: ae3f2abe06af Branch: None User: zzzeek Date: 2014-01-26 07:04:41 Summary: updates Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/4a7acd40ce39/ Changeset: 4a7acd40ce39 Branch: rel_0_8 User: zzzeek Date: 2014-01-26 07:04:46 Summary: updates 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.
