sqlalchemy-commits Mailing List for SQLAlchemy (Page 48)
Brought to you by:
zzzeek
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-02-06 01:41:04
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2f6138f10fc2/ Changeset: 2f6138f10fc2 Branch: ticket_3054 User: zzzeek Date: 2015-02-06 01:40:34+00:00 Summary: - use a much updated approach and API for baked - start adding tests 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-05 23:02:34
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/37c1571e1be1/ Changeset: 37c1571e1be1 Branch: ticket_3054 User: zzzeek Date: 2015-02-05 23:02:06+00:00 Summary: Merge branch 'master' into ticket_3054 Affected #: 229 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-05 21:25:14
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/503a40ad7080/ Changeset: 503a40ad7080 Branch: None User: zzzeek Date: 2015-02-05 21:24:45+00:00 Summary: - The MySQL dialect now renders TIMESTAMP with NULL / NOT NULL in all cases, so that MySQL 5.6.6 with the ``explicit_defaults_for_timestamp`` flag enabled will will allow TIMESTAMP to continue to work as expected when ``nullable=False``. Existing applications are unaffected as SQLAlchemy has always emitted NULL for a TIMESTAMP column that is ``nullable=True``. fixes #3155 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-02-04 23:52:29
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/068f9a1531c8/ Changeset: 068f9a1531c8 Branch: None User: zzzeek Date: 2015-02-04 23:51:24+00:00 Summary: - Fixed bug in :class:`.Connection` and pool where the :meth:`.Connection.invalidate` method, or an invalidation due to a database disconnect, would fail if the ``isolation_level`` parameter had been used with :meth:`.Connection.execution_options`; the "finalizer" that resets the isolation level would be called on the no longer opened connection. fixes #3302 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7c196d16fed5/ Changeset: 7c196d16fed5 Branch: rel_0_9 User: zzzeek Date: 2015-02-04 23:52:16+00:00 Summary: - Fixed bug in :class:`.Connection` and pool where the :meth:`.Connection.invalidate` method, or an invalidation due to a database disconnect, would fail if the ``isolation_level`` parameter had been used with :meth:`.Connection.execution_options`; the "finalizer" that resets the isolation level would be called on the no longer opened connection. fixes #3302 (cherry picked from commit 068f9a1531c8114360d5fcd964c27fe6a21f4679) 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-02-04 23:38:31
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9cbe235810b7/ Changeset: 9cbe235810b7 Branch: None User: zzzeek Date: 2015-02-04 23:35:01+00:00 Summary: - A warning is emitted if the ``isolation_level`` parameter is used with :meth:`.Connection.execution_options` when a :class:`.Transaction` is in play; DBAPIs and/or SQLAlchemy dialects such as psycopg2, MySQLdb may implicitly rollback or commit the transaction, or not change the setting til next transaction, so this is never safe. - Added new parameter :paramref:`.Session.connection.execution_options` which may be used to set up execution options on a :class:`.Connection` when it is first checked out, before the transaction has begun. This is used to set up options such as isolation level on the connection before the transaction starts. - added new documentation section detailing best practices for setting transaction isolation with sessions. fixes #3296 Affected #: 9 files https://bitbucket.org/zzzeek/sqlalchemy/commits/280497cc5bda/ Changeset: 280497cc5bda Branch: rel_0_9 User: zzzeek Date: 2015-02-04 23:37:51+00:00 Summary: - A warning is emitted if the ``isolation_level`` parameter is used with :meth:`.Connection.execution_options` when a :class:`.Transaction` is in play; DBAPIs and/or SQLAlchemy dialects such as psycopg2, MySQLdb may implicitly rollback or commit the transaction, or not change the setting til next transaction, so this is never safe. - Added new parameter :paramref:`.Session.connection.execution_options` which may be used to set up execution options on a :class:`.Connection` when it is first checked out, before the transaction has begun. This is used to set up options such as isolation level on the connection before the transaction starts. - added new documentation section detailing best practices for setting transaction isolation with sessions. fixes #3296 (cherry picked from commit 9cbe235810b7c0c24d2556b4bb581b0207812e2d) Conflicts: test/orm/test_bind.py 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...> - 2015-02-04 22:07:33
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b3e09f927e64/ Changeset: b3e09f927e64 Branch: 3296 User: zzzeek Date: 2015-02-04 22:07:15+00:00 Summary: wip 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-03 00:49:34
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9ea19b374630/ Changeset: 9ea19b374630 Branch: None User: zzzeek Date: 2015-02-03 00:46:13+00:00 Summary: - Fixed bug in lazy loading SQL construction whereby a complex primaryjoin that referred to the same "local" column multiple times in the "column that points to itself" style of self-referential join would not be substituted in all cases. The logic to determine substitutions here has been reworked to be more open-ended. fixes #3300 Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/19776f3585f8/ Changeset: 19776f3585f8 Branch: rel_0_9 User: zzzeek Date: 2015-02-03 00:49:10+00:00 Summary: - Fixed bug in lazy loading SQL construction whereby a complex primaryjoin that referred to the same "local" column multiple times in the "column that points to itself" style of self-referential join would not be substituted in all cases. The logic to determine substitutions here has been reworked to be more open-ended. fixes #3300 Conflicts: test/orm/test_relationships.py 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-02 23:22:52
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/54088c9b3380/ Changeset: 54088c9b3380 Branch: None User: zzzeek Date: 2015-02-02 17:58:24+00:00 Summary: - don't overwrite an existing _strategy_keys collection; this would cause LazyLoader to be initialized twice per property. 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-02 00:04:13
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/cf4e421248e3/ Changeset: cf4e421248e3 Branch: None User: kdeldycke Date: 2014-02-06 10:44:52+00:00 Summary: Add unit test for UUID arrays in PostgreSQL. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/02dbcfa88a83/ Changeset: 02dbcfa88a83 Branch: None User: zzzeek Date: 2015-02-01 23:43:34+00:00 Summary: Merge remote-tracking branch 'origin/pr/68' into pr68 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/b2189da65019/ Changeset: b2189da65019 Branch: None User: zzzeek Date: 2015-02-02 00:03:08+00:00 Summary: - Repaired support for Postgresql UUID types in conjunction with the ARRAY type when using psycopg2. The psycopg2 dialect now employs use of the psycopg2.extras.register_uuid() hook so that UUID values are always passed to/from the DBAPI as UUID() objects. The :paramref:`.UUID.as_uuid` flag is still honored, except with psycopg2 we need to convert returned UUID objects back into strings when this is disabled. fixes #2940 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/9e5c7627f6e7/ Changeset: 9e5c7627f6e7 Branch: None User: kdeldycke Date: 2015-02-02 00:03:48+00:00 Summary: Add unit test for UUID arrays in PostgreSQL. (cherry picked from commit cf4e421248e3175b97170d0c6930b360ff326c06) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/927f1cb95143/ Changeset: 927f1cb95143 Branch: rel_0_9 User: zzzeek Date: 2015-02-02 00:03:55+00:00 Summary: - Repaired support for Postgresql UUID types in conjunction with the ARRAY type when using psycopg2. The psycopg2 dialect now employs use of the psycopg2.extras.register_uuid() hook so that UUID values are always passed to/from the DBAPI as UUID() objects. The :paramref:`.UUID.as_uuid` flag is still honored, except with psycopg2 we need to convert returned UUID objects back into strings when this is disabled. fixes #2940 (cherry picked from commit b2189da65019ed2f44e77933a122619489319c5a) 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-01 00:07:26
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/e7d61d594b8a/ Changeset: e7d61d594b8a Branch: None User: Mateusz Susik Date: 2014-10-24 11:27:29+00:00 Summary: Psycopg2 JSONB support. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a523163c4140/ Changeset: a523163c4140 Branch: None User: zzzeek Date: 2015-01-31 22:53:02+00:00 Summary: Merge remote-tracking branch 'origin/pr/145' into pr145 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/bf70f556b382/ Changeset: bf70f556b382 Branch: None User: zzzeek Date: 2015-02-01 00:04:54+00:00 Summary: - Added support for the :class:`postgresql.JSONB` datatype when using psycopg2 2.5.4 or greater, which features native conversion of JSONB data so that SQLAlchemy's converters must be disabled; additionally, the newly added psycopg2 extension ``extras.register_default_jsonb`` is used to establish a JSON deserializer passed to the dialect via the ``json_deserializer`` argument. Also repaired the Postgresql integration tests which weren't actually round-tripping the JSONB type as opposed to the JSON type. Pull request courtesy Mateusz Susik. - Repaired the use of the "array_oid" flag when registering the HSTORE type with older psycopg2 versions < 2.4.3, which does not support this flag, as well as use of the native json serializer hook "register_default_json" with user-defined ``json_deserializer`` on psycopg2 versions < 2.5, which does not include native json. Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/9d8b0633cc6f/ Changeset: 9d8b0633cc6f Branch: None User: Mateusz Susik Date: 2015-02-01 00:05:55+00:00 Summary: Psycopg2 JSONB support. (cherry picked from commit e7d61d594b8a89535696436a667a526bd2999fb2) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/0bd74617f877/ Changeset: 0bd74617f877 Branch: rel_0_9 User: zzzeek Date: 2015-02-01 00:06:04+00:00 Summary: - Added support for the :class:`postgresql.JSONB` datatype when using psycopg2 2.5.4 or greater, which features native conversion of JSONB data so that SQLAlchemy's converters must be disabled; additionally, the newly added psycopg2 extension ``extras.register_default_jsonb`` is used to establish a JSON deserializer passed to the dialect via the ``json_deserializer`` argument. Also repaired the Postgresql integration tests which weren't actually round-tripping the JSONB type as opposed to the JSON type. Pull request courtesy Mateusz Susik. - Repaired the use of the "array_oid" flag when registering the HSTORE type with older psycopg2 versions < 2.4.3, which does not support this flag, as well as use of the native json serializer hook "register_default_json" with user-defined ``json_deserializer`` on psycopg2 versions < 2.5, which does not include native json. (cherry picked from commit bf70f556b382dc376783efbcb598e0fab71ee235) 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-01-30 18:58:46
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/383bb3f70816/ Changeset: 383bb3f70816 Branch: None User: zzzeek Date: 2015-01-30 18:38:51+00:00 Summary: - The :class:`.CheckConstraint` construct now supports naming conventions that include the token ``%(column_0_name)s``; the constraint expression is scanned for columns. Additionally, naming conventions for check constraints that don't include the ``%(constraint_name)s`` token will now work for :class:`.SchemaType`- generated constraints, such as those of :class:`.Boolean` and :class:`.Enum`; this stopped working in 0.9.7 due to :ticket:`3067`. fixes #3299 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-01-28 16:57:04
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3712e35c329c/ Changeset: 3712e35c329c Branch: None User: zzzeek Date: 2015-01-28 16:55:26+00:00 Summary: - Fixed bug in 0.9's foreign key setup system, such that the logic used to link a :class:`.ForeignKey` to its parent could fail when the foreign key used "link_to_name=True" in conjunction with a target :class:`.Table` that would not receive its parent column until later, such as within a reflection + "useexisting" scenario, if the target column in fact had a key value different from its name, as would occur in reflection if column reflect events were used to alter the .key of reflected :class:`.Column` objects so that the link_to_name becomes significant. Also repaired support for column type via FK transmission in a similar way when target columns had a different key and were referenced using link_to_name. fixes #3298 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/8a744a468486/ Changeset: 8a744a468486 Branch: rel_0_9 User: zzzeek Date: 2015-01-28 16:56:13+00:00 Summary: - Fixed bug in 0.9's foreign key setup system, such that the logic used to link a :class:`.ForeignKey` to its parent could fail when the foreign key used "link_to_name=True" in conjunction with a target :class:`.Table` that would not receive its parent column until later, such as within a reflection + "useexisting" scenario, if the target column in fact had a key value different from its name, as would occur in reflection if column reflect events were used to alter the .key of reflected :class:`.Column` objects so that the link_to_name becomes significant. Also repaired support for column type via FK transmission in a similar way when target columns had a different key and were referenced using link_to_name. fixes #3298 (cherry picked from commit 3712e35c329cc3b5106f026be90e04f65412586d) 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-01-27 05:34:54
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8aaa8dd6bdfb/ Changeset: 8aaa8dd6bdfb Branch: None User: zzzeek Date: 2015-01-27 05:34:10+00:00 Summary: - fix link to non_primary flag - rewrite the multiple mappers section Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/873c2a7f7a8b/ Changeset: 873c2a7f7a8b Branch: rel_0_9 User: zzzeek Date: 2015-01-27 05:34:36+00:00 Summary: - fix link to non_primary flag - rewrite the multiple mappers section 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-01-27 04:09:44
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/62f877490676/ Changeset: 62f877490676 Branch: None User: zzzeek Date: 2015-01-27 03:45:12+00:00 Summary: - fix this test for py3k 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-01-26 23:44:39
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f94d75ede5f5/ Changeset: f94d75ede5f5 Branch: None User: Shaun Stanworth Date: 2015-01-26 23:43:19+00:00 Summary: Added psycopg2cffi dialect Affected #: 10 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0953f2625046/ Changeset: 0953f2625046 Branch: None User: Shaun Stanworth Date: 2015-01-26 23:43:19+00:00 Summary: 78-char width Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/226bd8d7077c/ Changeset: 226bd8d7077c Branch: None User: Shaun Stanworth Date: 2015-01-26 23:43:19+00:00 Summary: Include psycopg2cffi in dialect docs Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a826ff366bf9/ Changeset: a826ff366bf9 Branch: None User: zzzeek Date: 2015-01-26 23:43:19+00:00 Summary: - additional test adjustments for pypy / psycopg2cffi. This consists mainly of adjusting fixtures to ensure connections are closed explicitly. psycopg2cffi also handles unicode bind parameter names differently than psycopg2, and seems to possibly have a little less control over floating point values at least in one test which is marked as a "fail", though will see if it runs differently on linux than osx.. - changelog for psycopg2cffi, fixes #3052 Affected #: 10 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-01-26 22:05:16
|
6 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9fb6acad6714/ Changeset: 9fb6acad6714 Branch: None User: f0rk Date: 2014-11-20 19:40:32+00:00 Summary: Report the type of unexpected expression objects Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0e61acaf145f/ Changeset: 0e61acaf145f Branch: None User: xflr6 Date: 2014-12-04 13:34:08+00:00 Summary: warn on duplicate polymorphic_identity Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0e6579bc6268/ Changeset: 0e6579bc6268 Branch: None User: zzzeek Date: 2015-01-26 21:49:43+00:00 Summary: Merge remote-tracking branch 'origin/pr/150' Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/20cdf0e8550e/ Changeset: 20cdf0e8550e Branch: None User: zzzeek Date: 2015-01-26 21:53:59+00:00 Summary: - changelog for pullreq github:150 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/54e68dc8bd4c/ Changeset: 54e68dc8bd4c Branch: None User: zzzeek Date: 2015-01-26 21:58:11+00:00 Summary: Merge branch 'bb_issue_3262' of https://bitbucket.org/xflr6/sqlalchemy Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/987f40b5aa32/ Changeset: 987f40b5aa32 Branch: None User: zzzeek Date: 2015-01-26 22:04:40+00:00 Summary: - changelog for #3262, fixes #3262 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-01-26 00:13:45
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/7b102eeaee12/ Changeset: 7b102eeaee12 Branch: None User: zzzeek Date: 2015-01-25 23:22:00+00:00 Summary: - remove the clever approach w/ dialect events, and remove the need for a for-loop through an empty tuple. we add one more local flag to handle the logic without repetition of dialect.do_execute() calls. 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-01-25 22:58:17
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a33c250da273/ Changeset: a33c250da273 Branch: None User: zzzeek Date: 2015-01-25 22:53:41+00:00 Summary: - remove context-specific post-crud logic from Connection and inline post-crud logic to some degree in DefaultExecutionContext. In particular we are removing post_insert() which doesn't appear to be used based on a survey of prominent third party dialects. Callcounts aren't added to existing execute profiling tests and inserts might be a little better. - simplify the execution_options join in DEC. Callcounts don't appear affected. 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-01-20 16:43:53
|
6 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/10dd5fe81062/ Changeset: 10dd5fe81062 Branch: None User: zzzeek Date: 2015-01-20 16:03:02+00:00 Summary: formatting Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/4032aaf097a9/ Changeset: 4032aaf097a9 Branch: None User: zzzeek Date: 2015-01-20 16:36:14+00:00 Summary: - enhance detail here regarding the difference between Connection.connection and engine.raw_connection() Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/2d27d777b11f/ Changeset: 2d27d777b11f Branch: None User: zzzeek Date: 2015-01-20 16:38:34+00:00 Summary: formatting (cherry picked from commit 10dd5fe81062347905492ef66e6f0453479cc03b) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/2d6b3fc41aeb/ Changeset: 2d6b3fc41aeb Branch: None User: zzzeek Date: 2015-01-20 16:38:41+00:00 Summary: - enhance detail here regarding the difference between Connection.connection and engine.raw_connection() (cherry picked from commit 4032aaf097a9268bc331e4b4815d77b19ba3febb) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/c3d898e8d06c/ Changeset: c3d898e8d06c Branch: None User: zzzeek Date: 2015-01-20 16:42:02+00:00 Summary: - Added new user-space accessors for viewing transaction isolation levels; :meth:`.Connection.get_isolation_level`, :attr:`.Connection.default_isolation_level`. - enhance documentation inter-linkage between new accessors, existing isolation_level parameters, as well as in the dialect-level methods which should be fully covered by Engine/Connection level APIs now. Affected #: 9 files https://bitbucket.org/zzzeek/sqlalchemy/commits/e4ed81dbe3eb/ Changeset: e4ed81dbe3eb Branch: rel_0_9 User: zzzeek Date: 2015-01-20 16:43:27+00:00 Summary: - Added new user-space accessors for viewing transaction isolation levels; :meth:`.Connection.get_isolation_level`, :attr:`.Connection.default_isolation_level`. - enhance documentation inter-linkage between new accessors, existing isolation_level parameters, as well as in the dialect-level methods which should be fully covered by Engine/Connection level APIs now. (cherry picked from commit c3d898e8d06c7e549bb273fc8654f5d24fab2204) 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...> - 2015-01-19 23:33:30
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/234a5b9723fb/ Changeset: 234a5b9723fb Branch: None User: zzzeek Date: 2015-01-19 23:31:10+00:00 Summary: - restore r611883ffb35ca6664649f6328ae8 with additional fixes and an additional test that is much more specific to #1326 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-01-19 23:00:48
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/26a1d8e77c26/ Changeset: 26a1d8e77c26 Branch: None User: zzzeek Date: 2015-01-19 23:00:21+00:00 Summary: - reverse the last commit temporarily as it breaks all the polymorphic cases 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-01-19 22:56:06
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/dacfe7dec2d9/ Changeset: dacfe7dec2d9 Branch: None User: zzzeek Date: 2015-01-19 22:37:14+00:00 Summary: - tests Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/611883ffb35c/ Changeset: 611883ffb35c Branch: None User: zzzeek Date: 2015-01-19 22:55:23+00:00 Summary: - The primary :class:`.Mapper` of a :class:`.Query` is now passed to the :meth:`.Session.get_bind` method when calling upon :meth:`.Query.count`, :meth:`.Query.update`, :meth:`.Query.delete`, as well as queries against mapped columns, :obj:`.column_property` objects, and SQL functions and expressions derived from mapped columns. This allows sessions that rely upon either customized :meth:`.Session.get_bind` schemes or "bound" metadata to work in all relevant cases. fixes #3227 fixes #3242 fixes #1326 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-01-19 16:47:53
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/6135c0323039/ Changeset: 6135c0323039 Branch: None User: zzzeek Date: 2015-01-19 16:47:28+00:00 Summary: - further fixes and even better tests for this block 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-01-19 13:50:06
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3f84a9408064/ Changeset: 3f84a9408064 Branch: None User: zzzeek Date: 2015-01-19 13:49:44+00:00 Summary: - another adjustment 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-01-19 04:33:42
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/28d0b8d1d1b1/ Changeset: 28d0b8d1d1b1 Branch: None User: zzzeek Date: 2015-01-19 04:32:52+00:00 Summary: - fix another issue from rf49c367ef, add another test 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. |