Thread: [Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets (Page 4)
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2014-01-03 00:08:14
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f188e28aea3b/ Changeset: f188e28aea3b Branch: None User: rschoon Date: 2014-01-01 02:46:31 Summary: Don't barf on Session(info=...) from sessionmaker(info=None) Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4f7469bbc131/ Changeset: 4f7469bbc131 Branch: None User: zzzeek Date: 2014-01-03 01:01:57 Summary: Merge bitbucket.org:rschoon/sqlalchemy into t Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7880d84c5b20/ Changeset: 7880d84c5b20 Branch: None User: zzzeek Date: 2014-01-03 01:07:13 Summary: - changelog for pullreq 9 from bitbucket 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-11 18:16:13
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2775c95b1ee3/ Changeset: 2775c95b1ee3 Branch: None User: zzzeek Date: 2014-01-11 19:12:40 Summary: new changelog Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6e4e1a83690e/ Changeset: 6e4e1a83690e Branch: None User: zzzeek Date: 2014-01-11 19:14:49 Summary: - add paramlinks and external changelog ext to 0.8 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a78110a21ccb/ Changeset: a78110a21ccb Branch: rel_0_8 User: zzzeek Date: 2014-01-11 19:15:23 Summary: pyo 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-13 00:44:57
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/86c3855c9baf/ Changeset: 86c3855c9baf Branch: None User: zzzeek Date: 2014-01-12 23:15:41 Summary: - bump up how many args for "named arg style" to four Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/c91fd822bc98/ Changeset: c91fd822bc98 Branch: None User: zzzeek Date: 2014-01-12 23:34:20 Summary: - add new event PoolEvents.invalidate(). allows interception of invalidation events including auto-invalidation, which is useful both for tests here as well as detecting failure conditions within the "reset" or "close" cases. - rename the argument for PoolEvents.reset() to dbapi_connection and connection_record to be consistent with everything else. - add new documentation sections on invalidation, including auto-invalidation and the invalidation process within the pool. - add _ConnectionFairy and _ConnectionRecord to the pool documentation. Establish docs for common _ConnectionFairy/_ConnectionRecord methods and accessors and have PoolEvents docs refer to _ConnectionRecord, since it is passed to all events. Rename a few _ConnectionFairy methods that are actually private to pool such as _checkout(), _checkin() and _checkout_existing(); there should not be any external code calling these Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/9c64607572a0/ Changeset: 9c64607572a0 Branch: None User: zzzeek Date: 2014-01-13 01:43:13 Summary: - :class:`.Connection` now associates a new :class:`.RootTransaction` or :class:`.TwoPhaseTransaction` with its immediate :class:`._ConnectionFairy` as a "reset handler" for the span of that transaction, which takes over the task of calling commit() or rollback() for the "reset on return" behavior of :class:`.Pool` if the transaction was not otherwise completed. This resolves the issue that a picky transaction like that of MySQL two-phase will be properly closed out when the connection is closed without an explicit rollback or commit (e.g. no longer raises "XAER_RMFAIL" in this case - note this only shows up in logging as the exception is not propagated within pool reset). This issue would arise e.g. when using an orm :class:`.Session` with ``twophase`` set, and then :meth:`.Session.close` is called without an explicit rollback or commit. The change also has the effect that you will now see an explicit "ROLLBACK" in the logs when using a :class:`.Session` object in non-autocommit mode regardless of how that session was discarded. Thanks to Jeff Dairiki and Laurence Rowe for isolating the issue here. [ticket:2907] 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-19 01:59:20
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0087ec728641/ Changeset: 0087ec728641 Branch: None User: zzzeek Date: 2014-01-19 02:56:56 Summary: akiban-> foundationdb Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/070c745a8697/ Changeset: 070c745a8697 Branch: None User: zzzeek Date: 2014-01-19 02:58:10 Summary: akiban-> foundationdb Conflicts: doc/build/dialects/index.rst Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/3509ea9685f9/ Changeset: 3509ea9685f9 Branch: rel_0_8 User: zzzeek Date: 2014-01-19 02:58:46 Summary: attic 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-23 17:41:03
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/aca8ffa474d1/ Changeset: aca8ffa474d1 Branch: None User: wichert Date: 2014-01-20 10:59:20 Summary: Remove uneeded import from code example This had me reread the code twice to see if I missed why the import was present. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9fef2c314bef/ Changeset: 9fef2c314bef Branch: None User: zzzeek Date: 2014-01-23 18:39:44 Summary: Merge pull request #60 from wichert/mutable-doc-import Remove uneeded import from code example Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/28fd486bd47b/ Changeset: 28fd486bd47b Branch: rel_0_8 User: wichert Date: 2014-01-23 18:40:18 Summary: Remove uneeded import from code example This had me reread the code twice to see if I missed why the import was present. 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-23 19:51:10
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/286657723151/ Changeset: 286657723151 Branch: rel_0_8 User: zzzeek Date: 2014-01-23 20:30:34 Summary: - add tests for [ticket:2918], confirm this is an 0.9 regression Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/15b23c7f71c0/ Changeset: 15b23c7f71c0 Branch: None User: zzzeek Date: 2014-01-23 20:49:04 Summary: - Fixed an 0.9 regression where the automatic aliasing applied by :class:`.Query` and in other situations where selects or joins were aliased (such as joined table inheritance) could fail if a user-defined :class:`.Column` subclass were used in the expression. In this case, the subclass would fail to propagate ORM-specific "annotations" along needed by the adaptation. The "expression annotations" system has been corrected to account for this case. [ticket:2918] Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/761511f3f241/ Changeset: 761511f3f241 Branch: None User: zzzeek Date: 2014-01-23 20:50:23 Summary: - remove this leftover commented pdb 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-25 21:39:18
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/38519e31b933/ Changeset: 38519e31b933 Branch: None User: zzzeek Date: 2014-01-25 22:37:30 Summary: seealsos in the tutorial Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/81a6e04f8a5b/ Changeset: 81a6e04f8a5b Branch: None User: zzzeek Date: 2014-01-25 22:37:49 Summary: imports Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a52b2da3d0a0/ Changeset: a52b2da3d0a0 Branch: rel_0_8 User: zzzeek Date: 2014-01-25 22:38:48 Summary: seealsos in the tutorial Conflicts: lib/sqlalchemy/sql/selectable.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...> - 2014-02-11 23:01:06
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/bd98bd5fffd5/ Changeset: bd98bd5fffd5 Branch: None User: Matt (work) Date: 2014-02-11 23:26:03 Summary: Parse server version info more robustly Closes #2934 Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/c036cca67e13/ Changeset: c036cca67e13 Branch: None User: zzzeek Date: 2014-02-11 23:57:40 Summary: Merge pull request #69 from sloat/pr2934 Fixes server version parsing in cymysql dialect Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/0050a8d3db04/ Changeset: 0050a8d3db04 Branch: None User: zzzeek Date: 2014-02-12 00:00:10 Summary: - changelog for [ticket:2934] 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-16 17:48:21
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/9d5188b1926d/ Changeset: 9d5188b1926d Branch: None User: zzzeek Date: 2014-02-16 18:43:46 Summary: - add cross-linking for passive_deletes / passive_updates Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0dc4beaa08b9/ Changeset: 0dc4beaa08b9 Branch: rel_0_8 User: zzzeek Date: 2014-02-16 18:47:19 Summary: - add cross-linking for passive_deletes / passive_updates Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/945b87b2d868/ Changeset: 945b87b2d868 Branch: None User: zzzeek Date: 2014-02-16 18:47:43 Summary: remove redundant see 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. |
From: Bitbucket <com...@bi...> - 2014-02-16 19:44:26
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/1921e7a3cbff/ Changeset: 1921e7a3cbff Branch: None User: zzzeek Date: 2014-02-16 20:28:56 Summary: - extensive cross-linking of relationship options with their documentation sections - convert all paramter references in relationship documentation to :paramref: Affected #: 8 files https://bitbucket.org/zzzeek/sqlalchemy/commits/dd6362aed772/ Changeset: dd6362aed772 Branch: rel_0_8 User: zzzeek Date: 2014-02-16 20:41:53 Summary: - extensive cross-linking of relationship options with their documentation sections - convert all paramter references in relationship documentation to :paramref: Conflicts: doc/build/orm/relationships.rst lib/sqlalchemy/ext/declarative/__init__.py lib/sqlalchemy/orm/relationships.py Affected #: 8 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a79efa2aa48f/ Changeset: a79efa2aa48f Branch: None User: zzzeek Date: 2014-02-16 20:43:26 Summary: this isn't really the mainstream use case here; would need to talk about non-equality operators in general. 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-16 21:42:32
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c7af5618dc95/ Changeset: c7af5618dc95 Branch: None User: Terentev Date: 2014-02-03 13:25:18 Summary: python_type for ARRAY (PGArray) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d54ba44c2ce2/ Changeset: d54ba44c2ce2 Branch: None User: zzzeek Date: 2014-02-16 22:40:04 Summary: Merge pull request #64 from LevonXXL/master python_type for ARRAY (PGArray) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/937e81be1645/ Changeset: 937e81be1645 Branch: None User: zzzeek Date: 2014-02-16 22:41:36 Summary: - changelog for pullreq github:64 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-16 23:29:26
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/a7e0d3e1e360/ Changeset: a7e0d3e1e360 Branch: None User: Roman Podoliaka Date: 2014-02-14 13:09:21 Summary: Fix unique constraints reflection in SQLite Reflection of unique constraints didn't work properly, if reserved identifiers had been used as column names. In this case column names would be put in double quotes (e.g. the name of column asc would be returned as "asc"). This issue is only present in 0.8.4 and not in 0.9.x. Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/28ec4fdfc838/ Changeset: 28ec4fdfc838 Branch: None User: zzzeek Date: 2014-02-17 00:19:55 Summary: Merge branch 'fix_sqlite_uc_reflection' of https://github.com/malor/sqlalchemy into t Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/beb567ba6f01/ Changeset: beb567ba6f01 Branch: None User: zzzeek Date: 2014-02-17 00:28:35 Summary: - changelog for pullreq github:72. Affected #: 1 file Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |
From: Bitbucket <com...@bi...> - 2014-02-19 21:07:48
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/4f29ebc72866/ Changeset: 4f29ebc72866 Branch: None User: zzzeek Date: 2014-02-19 22:02:29 Summary: - Support has been improved for Postgresql reflection behavior on very old (pre 8.1) versions of Postgresql, and potentially other PG engines such as Redshift (assuming Redshift reports the version as < 8.1). The query for "indexes" as well as "primary keys" relies upon inspecting a so-called "int2vector" datatype, which refuses to coerce to an array prior to 8.1 causing failures regarding the "ANY()" operator used in the query. Extensive googling has located the very hacky, but recommended-by-PG-core-developer query to use when PG version < 8.1 is in use, so index and primary key constraint reflection now work on these versions. Conflicts: doc/build/changelog/changelog_09.rst test/dialect/postgresql/test_types.py Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/033463cd4bd9/ Changeset: 033463cd4bd9 Branch: None User: zzzeek Date: 2014-02-19 22:03:05 Summary: backport Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0d81c6c7a311/ Changeset: 0d81c6c7a311 Branch: rel_0_8 User: zzzeek Date: 2014-02-19 22:07:01 Summary: - add improved support here for string parsing of predicates, backport from 0.9 Affected #: 1 file Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |
From: Bitbucket <com...@bi...> - 2014-02-26 20:47:09
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/bf67069d264c/ Changeset: bf67069d264c Branch: None User: zzzeek Date: 2014-02-26 19:28:14 Summary: - Fixed issue in new :meth:`.TextClause.columns` method where the ordering of columns given positionally would not be preserved. This could have potential impact in positional situations such as applying the resulting :class:`.TextAsFrom` object to a union. Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/302ad6228a12/ Changeset: 302ad6228a12 Branch: None User: zzzeek Date: 2014-02-26 21:34:49 Summary: - Some changes to how the :attr:`.FromClause.c` collection behaves when presented with duplicate columns. The behavior of emitting a warning and replacing the old column with the same name still remains to some degree; the replacement in particular is to maintain backwards compatibility. However, the replaced column still remains associated with the ``c`` collection now in a collection ``._all_columns``, which is used by constructs such as aliases and unions, to deal with the set of columns in ``c`` more towards what is actually in the list of columns rather than the unique set of key names. This helps with situations where SELECT statements with same-named columns are used in unions and such, so that the union can match the columns up positionally and also there's some chance of :meth:`.FromClause.corresponding_column` still being usable here (it can now return a column that is only in selectable.c._all_columns and not otherwise named). The new collection is underscored as we still need to decide where this list might end up. Theoretically it would become the result of iter(selectable.c), however this would mean that the length of the iteration would no longer match the length of keys(), and that behavior needs to be checked out. fixes #2974 - add a bunch more tests for ColumnCollection Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6aeec027a0fb/ Changeset: 6aeec027a0fb Branch: None User: zzzeek Date: 2014-02-26 21:45:52 Summary: - Adjusted the logic which applies names to the .c collection when a no-name :class:`.BindParameter` is received, e.g. via :func:`.sql.literal` or similar; the "key" of the bind param is used as the key within .c. rather than the rendered name. Since these binds have "anonymous" names in any case, this allows individual bound parameters to have their own name within a selectable if they are otherwise unlabeled. fixes #2974 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-02-27 00:29:18
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2d146ddad97e/ Changeset: 2d146ddad97e Branch: None User: zzzeek Date: 2014-02-27 01:27:22 Summary: - Removed stale names from ``sqlalchemy.orm.interfaces.__all__`` and refreshed with current names, so that an ``import *`` from this module again works. fixes #2975 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a3ad92de4b1b/ Changeset: a3ad92de4b1b Branch: None User: zzzeek Date: 2014-02-27 01:27:47 Summary: - Removed stale names from ``sqlalchemy.orm.interfaces.__all__`` and refreshed with current names, so that an ``import *`` from this module again works. fixes #2975 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/3dca38608bde/ Changeset: 3dca38608bde Branch: rel_0_8 User: zzzeek Date: 2014-02-27 01:27:57 Summary: 0.8.6 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-03-03 01:34:41
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/bd36703acfb3/ Changeset: bd36703acfb3 Branch: None User: zzzeek Date: 2014-03-02 23:09:47 Summary: save some various scratch work for trying to make __multiple__ work Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/eb7a788364c2/ Changeset: eb7a788364c2 Branch: None User: zzzeek Date: 2014-03-03 00:55:37 Summary: - break out all the test extensions from being nose-specific and begin getting them all compatible with py.test as well Affected #: 7 files https://bitbucket.org/zzzeek/sqlalchemy/commits/746789942521/ Changeset: 746789942521 Branch: multi_db_tests User: zzzeek Date: 2014-03-03 02:34:21 Summary: - working through this.. 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-03-03 02:07:43
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ae522f08e6bb/ Changeset: ae522f08e6bb Branch: None User: zzzeek Date: 2014-03-03 02:39:07 Summary: that seems to work Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/d00f6069d0a2/ Changeset: d00f6069d0a2 Branch: None User: zzzeek Date: 2014-03-03 03:02:06 Summary: updates Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/28dd27972be6/ Changeset: 28dd27972be6 Branch: multi_db_tests User: zzzeek Date: 2014-03-03 03:07:27 Summary: we dont need to trick the importer! wow 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-03-05 23:59:51
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/c4dede6e7c14/ Changeset: c4dede6e7c14 Branch: None User: cito Date: 2014-02-27 21:15:21 Summary: Restore coercion to unicode with cx_Oracle. This feature is now turned off by default. Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/321a668ccd83/ Changeset: 321a668ccd83 Branch: None User: zzzeek Date: 2014-03-06 00:16:11 Summary: Merge branch 'master' of https://github.com/Cito/sqlalchemy into t Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/4175ca20508b/ Changeset: 4175ca20508b Branch: None User: zzzeek Date: 2014-03-06 00:58:37 Summary: - changelog for pullreq github:74 - various improvemnts to oracle docs, rewrite section on unicode, more linking, enhance section on resolve_synonyms 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-03-17 20:26:46
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ce3505ea8b3a/ Changeset: ce3505ea8b3a Branch: None User: zzzeek Date: 2014-03-16 19:51:47 Summary: typo Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/9ec01ab35a6c/ Changeset: 9ec01ab35a6c Branch: None User: zzzeek Date: 2014-03-17 21:25:51 Summary: - Improved an error message which would occur if a query() were made against a non-selectable, such as a :func:`.literal_column`, and then an attempt was made to use :meth:`.Query.join` such that the "left" side would be determined as ``None`` and then fail. This condition is now detected explicitly. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/987759aec51e/ Changeset: 987759aec51e Branch: rel_0_8 User: zzzeek Date: 2014-03-17 21:26:09 Summary: - Improved an error message which would occur if a query() were made against a non-selectable, such as a :func:`.literal_column`, and then an attempt was made to use :meth:`.Query.join` such that the "left" side would be determined as ``None`` and then fail. This condition is now detected explicitly. 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-03-17 21:28:47
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/fbfad42cb47f/ Changeset: fbfad42cb47f Branch: None User: Charles-Axel Dein Date: 2014-03-15 22:42:43 Summary: Add is_ and isnot filter to the tutorial Most linter complain when comparing with None. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/fd8dbf8e7898/ Changeset: fd8dbf8e7898 Branch: None User: zzzeek Date: 2014-03-17 22:27:21 Summary: Merge branch 'ca/dev/add_is_and_isnot_to_tutorial' of https://github.com/charlax/sqlalchemy Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/c5005f7e4b11/ Changeset: c5005f7e4b11 Branch: rel_0_8 User: Charles-Axel Dein Date: 2014-03-17 22:28:05 Summary: Add is_ and isnot filter to the tutorial Most linter complain when comparing with None. 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-03-22 20:37:25
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/0bb00db55812/ Changeset: 0bb00db55812 Branch: None User: Roman Podoliaka Date: 2014-03-13 01:56:42 Summary: Remove tables from metadata when autoload fails If autoloading of a table fails, don't register it in a metadata instance. It seems that the original behaviour was accidentally changed in f6198d9abf453182f4b111e0579a7a4ef1614e79, restore it. Closes issue #2988 Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/8459c27273ec/ Changeset: 8459c27273ec Branch: None User: zzzeek Date: 2014-03-22 21:34:51 Summary: Merge branch 'fix_table_registration' of https://github.com/malor/sqlalchemy into t Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/c464960fddf0/ Changeset: c464960fddf0 Branch: None User: zzzeek Date: 2014-03-22 21:36:06 Summary: changelog to fix #2988 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-03-22 21:51:38
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/ec97911ed915/ Changeset: ec97911ed915 Branch: None User: zzzeek Date: 2014-03-22 22:31:50 Summary: - Adjusted ``setup.py`` file to support the possible future removal of the ``setuptools.Feature`` extension from setuptools. If this keyword isn't present, the setup will still succeed with setuptools rather than falling back to distutils. C extension building can be disabled now also by setting the DISABLE_SQLALCHEMY_CEXT environment variable. This variable works whether or not setuptools is even available. fixes #2986 - using platform.python_implementation() in setup.py to detect CPython. I've tested this function on OSX and linux on Python 2.6 through 3.4, including 3.1, 3.2, 3.3. Unfortunately, on OSX + 3.2 only, it seems to segfault. I've tried installing 3.2.5 from the python.org .dmg, building it from source, and also blew away the whole 3.2 directory, something seems to be wrong with the "platform" module on that platform only, and there's also no issue on bugs.python.org; however, I'm going with it anyway. If someone is using 3.2 on OSX they really should be upgrading. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/0dddcf924ead/ Changeset: 0dddcf924ead Branch: rel_0_8 User: zzzeek Date: 2014-03-22 22:47:07 Summary: - Adjusted ``setup.py`` file to support the possible future removal of the ``setuptools.Feature`` extension from setuptools. If this keyword isn't present, the setup will still succeed with setuptools rather than falling back to distutils. C extension building can be disabled now also by setting the DISABLE_SQLALCHEMY_CEXT environment variable. This variable works whether or not setuptools is even available. fixes #2986 - using platform.python_implementation() in setup.py to detect CPython. I've tested this function on OSX and linux on Python 2.6 through 3.4, including 3.1, 3.2, 3.3. Unfortunately, on OSX + 3.2 only, it seems to segfault. I've tried installing 3.2.5 from the python.org .dmg, building it from source, and also blew away the whole 3.2 directory, something seems to be wrong with the "platform" module on that platform only, and there's also no issue on bugs.python.org; however, I'm going with it anyway. If someone is using 3.2 on OSX they really should be upgrading. - adjusted the logic for platform_implementation(), apparently "platform" is there in python 2.5, so we are doing a version check. Conflicts: doc/build/intro.rst setup.py Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/56ef17e0f7b4/ Changeset: 56ef17e0f7b4 Branch: None User: zzzeek Date: 2014-03-22 22:49:35 Summary: - we aren't supporting py2.5 so just simplify this import for platform, re: #2986 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-03-22 23:34:50
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8e10ab92df0d/ Changeset: 8e10ab92df0d Branch: None User: zzzeek Date: 2014-03-23 00:02:37 Summary: - restore the old behavior of the connection pool replacing itself just within userland engine.dispose(); as some SQLA tests already failed when the replace step was removed, due to those conns still being referenced, it's likely this will create surprises for all those users that incorrectly use dispose() and it's not really worth dealing with. This doesn't affect the change we made for ref: #2985. Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a7a6b436600c/ Changeset: a7a6b436600c Branch: None User: zzzeek Date: 2014-03-23 00:10:00 Summary: there's no "assert_call_count" on mock Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/b00e15b50f83/ Changeset: b00e15b50f83 Branch: None User: zzzeek Date: 2014-03-23 00:34:18 Summary: - An event listener can now be associated with a :class:`.Engine`, after one or more :class:`.Connection` objects have been created (such as by an orm :class:`.Session` or via explicit connect) and the listener will pick up events from those connections. Previously, performance concerns pushed the event transfer from :class:`.Engine` to :class:`.Connection` at init-time only, but we've inlined a bunch of conditional checks to make this possible without any additional function calls. fixes #2978 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-04-02 22:14:37
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b23bb79581ff/ Changeset: b23bb79581ff Branch: None User: zzzeek Date: 2014-04-03 00:11:11 Summary: - reverse order of columns in sample CTEs as this is a UNION and the cols need to line up - alter this in the unit tests as well as these queries were just copied from the tests - remove the included_parts.join(parts) from the core CTE doc (also just copied from the test, where we want to make sure joins don't get screwed up with the CTE) as it doesn't contribute to the query itself fixes #3014 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/df7fe021a945/ Changeset: df7fe021a945 Branch: rel_0_8 User: zzzeek Date: 2014-04-03 00:13:52 Summary: - reverse order of columns in sample CTEs as this is a UNION and the cols need to line up - alter this in the unit tests as well as these queries were just copied from the tests - remove the included_parts.join(parts) from the core CTE doc (also just copied from the test, where we want to make sure joins don't get screwed up with the CTE) as it doesn't contribute to the query itself fixes #3014 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/aba956a85dc0/ Changeset: aba956a85dc0 Branch: None User: zzzeek Date: 2014-04-03 00:14:10 Summary: escape backslash 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-04-11 18:54:10
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/10ea59241feb/ Changeset: 10ea59241feb Branch: None User: Daniel Smith Date: 2014-04-11 01:15:17 Summary: Fixed bug in example code. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/a48217b13575/ Changeset: a48217b13575 Branch: None User: zzzeek Date: 2014-04-11 20:53:20 Summary: Merge pull request #84 from Daniel-B-Smith/master Fixed bug in example code on orm session page. Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/280758acc5ca/ Changeset: 280758acc5ca Branch: rel_0_8 User: Daniel Smith Date: 2014-04-11 20:53:49 Summary: Fixed bug in example code. 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. |