sqlalchemy-commits Mailing List for SQLAlchemy (Page 49)
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-01-19 01:58:15
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f5d4f2685f30/ Changeset: f5d4f2685f30 Branch: None User: zzzeek Date: 2015-01-19 01:57:26+00:00 Summary: - rework assertsql system, fixes #3293 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-18 03:00:27
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f49c367ef712/ Changeset: f49c367ef712 Branch: None User: zzzeek Date: 2015-01-18 02:58:49+00:00 Summary: - fix a regression from ref #3178, where dialects that don't actually support sane multi rowcount (e.g. pyodbc) would fail on multirow update. add a test that mocks this breakage into plain dialects 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-17 17:50:22
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/469b6fabaf78/ Changeset: 469b6fabaf78 Branch: None User: zzzeek Date: 2015-01-17 17:46:20+00:00 Summary: - add an exclusion here that helps with the case of 3rd party test suite redefining an existing test in test_suite Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/96ef0bf768c8/ Changeset: 96ef0bf768c8 Branch: rel_0_9 User: zzzeek Date: 2015-01-17 17:48:17+00:00 Summary: - add an exclusion here that helps with the case of 3rd party test suite redefining an existing test in test_suite Conflicts: lib/sqlalchemy/testing/plugin/pytestplugin.py 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-17 01:04:45
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/f3a892a3ef66/ Changeset: f3a892a3ef66 Branch: None User: zzzeek Date: 2015-01-17 01:03:33+00:00 Summary: - Custom dialects that implement :class:`.GenericTypeCompiler` can now be constructed such that the visit methods receive an indication of the owning expression object, if any. Any visit method that accepts keyword arguments (e.g. ``**kw``) will in most cases receive a keyword argument ``type_expression``, referring to the expression object that the type is contained within. For columns in DDL, the dialect's compiler class may need to alter its ``get_column_specification()`` method to support this as well. The ``UserDefinedType.get_col_spec()`` method will also receive ``type_expression`` if it provides ``**kw`` in its argument signature. fixes #3074 Affected #: 13 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-16 23:04:24
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/79fa69f1f37f/ Changeset: 79fa69f1f37f Branch: None User: zzzeek Date: 2015-01-16 23:03:45+00:00 Summary: - Fixed bug where Postgresql dialect would fail to render an expression in an :class:`.Index` that did not correspond directly to a table-bound column; typically when a :func:`.text` construct was one of the expressions within the index; or could misinterpret the list of expressions if one or more of them were such an expression. fixes #3174 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/63b2c466d12f/ Changeset: 63b2c466d12f Branch: rel_0_9 User: zzzeek Date: 2015-01-16 23:04:07+00:00 Summary: - Fixed bug where Postgresql dialect would fail to render an expression in an :class:`.Index` that did not correspond directly to a table-bound column; typically when a :func:`.text` construct was one of the expressions within the index; or could misinterpret the list of expressions if one or more of them were such an expression. fixes #3174 (cherry picked from commit 79fa69f1f37fdbc0dfec6bdea1e07f52bfe18f7b) 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-13 22:09:33
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b63aae2c232f/ Changeset: b63aae2c232f Branch: None User: zzzeek Date: 2015-01-13 22:04:35+00:00 Summary: - The "wildcard" loader options, in particular the one set up by the :func:`.orm.load_only` option to cover all attributes not explicitly mentioned, now takes into account the superclasses of a given entity, if that entity is mapped with inheritance mapping, so that attribute names within the superclasses are also omitted from the load. Additionally, the polymorphic discriminator column is unconditionally included in the list, just in the same way that primary key columns are, so that even with load_only() set up, polymorphic loading of subtypes continues to function correctly. fixes #3287 Affected #: 6 files https://bitbucket.org/zzzeek/sqlalchemy/commits/11383dae8d14/ Changeset: 11383dae8d14 Branch: rel_0_9 User: zzzeek Date: 2015-01-13 22:09:16+00:00 Summary: - The "wildcard" loader options, in particular the one set up by the :func:`.orm.load_only` option to cover all attributes not explicitly mentioned, now takes into account the superclasses of a given entity, if that entity is mapped with inheritance mapping, so that attribute names within the superclasses are also omitted from the load. Additionally, the polymorphic discriminator column is unconditionally included in the list, just in the same way that primary key columns are, so that even with load_only() set up, polymorphic loading of subtypes continues to function correctly. fixes #3287 (cherry picked from commit b63aae2c232f980a47aa2a635c35dfa45390f451) Conflicts: lib/sqlalchemy/orm/mapper.py Affected #: 6 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |
From: Bitbucket <com...@bi...> - 2015-01-13 20:17:32
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/268bb4d5f6a8/ Changeset: 268bb4d5f6a8 Branch: None User: zzzeek Date: 2015-01-13 20:17:09+00:00 Summary: - refine the previous commit a bit 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-13 19:34:13
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/92cc232726a0/ Changeset: 92cc232726a0 Branch: None User: zzzeek Date: 2015-01-13 19:33:33+00:00 Summary: - The multi-values version of :meth:`.Insert.values` has been repaired to work more usefully with tables that have Python- side default values and/or functions, as well as server-side defaults. The feature will now work with a dialect that uses "positional" parameters; a Python callable will also be invoked individually for each row just as is the case with an "executemany" style invocation; a server- side default column will no longer implicitly receive the value explicitly specified for the first row, instead refusing to invoke without an explicit value. fixes #3288 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-01-06 16:45:44
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b8a8cdd1ff47/ Changeset: b8a8cdd1ff47 Branch: None User: zzzeek Date: 2015-01-06 16:45:17+00:00 Summary: - doc fixes Affected #: 2 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |
From: Bitbucket <com...@bi...> - 2015-01-06 16:37:25
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/67778e20624b/ Changeset: 67778e20624b Branch: None User: zzzeek Date: 2015-01-06 16:34:52+00:00 Summary: - add a close here Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/f06a1bb50ae6/ Changeset: f06a1bb50ae6 Branch: rel_0_9 User: zzzeek Date: 2015-01-06 16:37:10+00:00 Summary: - add a close here Affected #: 1 file Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |
From: Bitbucket <com...@bi...> - 2015-01-06 02:42:31
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/57f684b4b4a6/ Changeset: 57f684b4b4a6 Branch: None User: zzzeek Date: 2015-01-06 02:38:19+00:00 Summary: - Fixed bug where if an exception were thrown at the start of a :class:`.Query` before it fetched results, particularly when row processors can't be formed, the cursor would stay open with results pending and not actually be closed. This is typically only an issue on an interpreter like Pypy where the cursor isn't immediately GC'ed, and can in some circumstances lead to transactions/ locks being open longer than is desirable. fixes #3285 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/93978ce3ae84/ Changeset: 93978ce3ae84 Branch: rel_0_9 User: zzzeek Date: 2015-01-06 02:42:10+00:00 Summary: - Fixed bug where if an exception were thrown at the start of a :class:`.Query` before it fetched results, particularly when row processors can't be formed, the cursor would stay open with results pending and not actually be closed. This is typically only an issue on an interpreter like Pypy where the cursor isn't immediately GC'ed, and can in some circumstances lead to transactions/ locks being open longer than is desirable. fixes #3285 Conflicts: lib/sqlalchemy/orm/loading.py 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-06 00:07:52
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/145d0151515d/ Changeset: 145d0151515d Branch: None User: zzzeek Date: 2015-01-06 00:07:33+00:00 Summary: fix verbiage 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-06 00:03:03
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/1104dcaa6706/ Changeset: 1104dcaa6706 Branch: None User: zzzeek Date: 2015-01-06 00:02:08+00:00 Summary: - add MemoizedSlots, a generalized solution to using __getattr__ for memoization on a class that uses slots. - apply many more __slots__. mem use for nova now at 46% savings Affected #: 18 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-05 19:21:35
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/41ae0270d997/ Changeset: 41ae0270d997 Branch: None User: zzzeek Date: 2015-01-05 19:20:03+00:00 Summary: - make a new page that introduces mapping a little better for the "mapping" section, contrasts declarative and classical some more Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/6552fb2ac04c/ Changeset: 6552fb2ac04c Branch: rel_0_9 User: zzzeek Date: 2015-01-05 19:21:11+00:00 Summary: - make a new page that introduces mapping a little better for the "mapping" section, contrasts declarative and classical some more Conflicts: doc/build/orm/mapper_config.rst 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-01-05 17:21:51
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8257b3a0173b/ Changeset: 8257b3a0173b Branch: None User: zzzeek Date: 2015-01-05 17:21:14+00:00 Summary: - more callcounts - add the platform key to the error output 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-05 02:06:44
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2a28dd93698b/ Changeset: 2a28dd93698b Branch: None User: zzzeek Date: 2015-01-05 02:01:27+00:00 Summary: - callcounts - this needs to be serializable and isn't high volume so just whack the slots Affected #: 2 files https://bitbucket.org/zzzeek/sqlalchemy/commits/a3241649332e/ Changeset: a3241649332e Branch: None User: zzzeek Date: 2015-01-05 02:05:53+00:00 Summary: - this is passing, no idea why 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-05 00:44:16
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/2f6ec41dc98c/ Changeset: 2f6ec41dc98c Branch: None User: zzzeek Date: 2015-01-05 00:43:48+00:00 Summary: - fix test for new events 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-05 00:29:24
|
5 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/cf272325635c/ Changeset: cf272325635c Branch: None User: zzzeek Date: 2015-01-04 23:06:02+00:00 Summary: - wip - start factoring events so that we aren't using descriptors for dispatch, allowing us to move to __slots__ Affected #: 8 files https://bitbucket.org/zzzeek/sqlalchemy/commits/27816e8f61b8/ Changeset: 27816e8f61b8 Branch: None User: zzzeek Date: 2015-01-04 23:30:25+00:00 Summary: - strategies + declarative Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/46a35b7647ac/ Changeset: 46a35b7647ac Branch: None User: zzzeek Date: 2015-01-04 23:45:30+00:00 Summary: - clean up default comparator which doesn't need to be a class, get PG stuff working Affected #: 4 files https://bitbucket.org/zzzeek/sqlalchemy/commits/b3bf7915b59c/ Changeset: b3bf7915b59c Branch: None User: zzzeek Date: 2015-01-05 00:05:31+00:00 Summary: - scale back _Dispatch and _JoinedDispatcher to use a __getitem__ scheme to start up listener collections; this pulls the overhead off of construction and makes performance much like the descriptor version, while still allowing slots. Fix up some profiles. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/18d3dc716390/ Changeset: 18d3dc716390 Branch: None User: zzzeek Date: 2015-01-05 00:28:29+00:00 Summary: - Structural memory use has been improved via much more significant use of ``__slots__`` for many internal objects. This optimization is particularly geared towards the base memory size of large applications that have lots of tables and columns, and greatly reduces memory size for a variety of high-volume objects including event listening internals, comparator objects and parts of the ORM attribute and loader strategy system. 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-04 06:54:56
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/b1928d72098d/ Changeset: b1928d72098d Branch: None User: zzzeek Date: 2015-01-04 04:22:07+00:00 Summary: - use a different bitwise approach here that doesn't require iterating through all possible set values Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/315db703a63f/ Changeset: 315db703a63f Branch: slots User: zzzeek Date: 2015-01-04 06:53:42+00:00 Summary: - start trying to move things into __slots__. This seems to reduce the size of the many per-column objects we're hitting, but somehow the overall memory is hardly being reduced at all in initial testing Affected #: 12 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-04 01:44:26
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/01a22a673ece/ Changeset: 01a22a673ece Branch: None User: zzzeek Date: 2015-01-03 23:49:14+00:00 Summary: - clean up SET tests Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/93742b3d5c16/ Changeset: 93742b3d5c16 Branch: None User: zzzeek Date: 2015-01-04 01:43:45+00:00 Summary: - The :class:`.mysql.SET` type has been overhauled to no longer assume that the empty string, or a set with a single empty string value, is in fact a set with a single empty string; instead, this is by default treated as the empty set. In order to handle persistence of a :class:`.mysql.SET` that actually wants to include the blank value ``''`` as a legitimate value, a new bitwise operational mode is added which is enabled by the :paramref:`.mysql.SET.retrieve_as_bitwise` flag, which will persist and retrieve values unambiguously using their bitflag positioning. Storage and retrieval of unicode values for driver configurations that aren't converting unicode natively is also repaired. fixes #3283 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-03 17:10:58
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/bb40221a2873/ Changeset: bb40221a2873 Branch: None User: zzzeek Date: 2015-01-03 17:10:17+00:00 Summary: - tighten the inspection in _ColumnEntity to reduce unnecessary isinstance() calls, express intent more clearly 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-02 21:43:34
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/378ad7971339/ Changeset: 378ad7971339 Branch: None User: zzzeek Date: 2015-01-02 21:43:11+00:00 Summary: - put this back now that we found the source of this 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-02 20:24:02
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/3ab50ec0118d/ Changeset: 3ab50ec0118d Branch: None User: zzzeek Date: 2015-01-02 20:23:24+00:00 Summary: - test failures: - test_schema_2 is only on PG and doesn't need a drop all, omit this for now - py3k has exception.args[0], not message 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-02 15:08:42
|
1 new commit in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/8582bbc5ecd6/ Changeset: 8582bbc5ecd6 Branch: None User: zzzeek Date: 2015-01-02 15:08:21+00:00 Summary: - repair drop_all_tables 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-02 01:17:44
|
3 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/da1aa2590851/ Changeset: da1aa2590851 Branch: None User: zzzeek Date: 2015-01-01 18:14:05+00:00 Summary: - remove the "edges" from the message here. It's illegible Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/8f5e4acbf693/ Changeset: 8f5e4acbf693 Branch: None User: zzzeek Date: 2015-01-01 18:39:42+00:00 Summary: - Added a new accessor :attr:`.Table.foreign_key_constraints` to complement the :attr:`.Table.foreign_keys` collection, as well as :attr:`.ForeignKeyConstraint.referred_table`. Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/21f47124ab43/ Changeset: 21f47124ab43 Branch: None User: zzzeek Date: 2015-01-02 01:17:06+00:00 Summary: - restate sort_tables in terms of a more fine grained sort_tables_and_constraints function. - The DDL generation system of :meth:`.MetaData.create_all` and :meth:`.Metadata.drop_all` has been enhanced to in most cases automatically handle the case of mutually dependent foreign key constraints; the need for the :paramref:`.ForeignKeyConstraint.use_alter` flag is greatly reduced. The system also works for constraints which aren't given a name up front; only in the case of DROP is a name required for at least one of the constraints involved in the cycle. fixes #3282 Affected #: 17 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. |