sqlalchemy-commits — SVN commits logged to this list

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - fix the uuid routine here to not run out of uuids

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/82a67abf4b5a/
Changeset:   82a67abf4b5a
Branch:      None
User:        zzzeek
Date:        2014-03-24 16:57:38
Summary:     - fix the uuid routine here to not run out of uuids

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - fix some doctest failures (though some remain, as it's not easy to get doctest

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/7e6a5e794624/
Changeset:   7e6a5e794624
Branch:      None
User:        zzzeek
Date:        2014-03-24 16:48:18
Summary:     - fix some doctest failures (though some remain, as it's not easy to get doctest
to accept things flexibly), fix #2999

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - rename __multiple__ to __backend__, and apply __backend__ to a large number of tests.

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2f150bee2852/
Changeset:   2f150bee2852
Branch:      master
User:        zzzeek
Date:        2014-03-24 16:33:53
Summary:     - rename __multiple__ to __backend__, and apply __backend__ to a large number of tests.
- move out logging tests from test_execute to test_logging

Affected #:  33 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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ebd24974f47f/
Changeset:   ebd24974f47f
Branch:      None
User:        zzzeek
Date:        2014-03-24 15:09:07
Summary:     take out accidental PG dialect use here

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/87d7076b49ec/
Changeset:   87d7076b49ec
Branch:      master
User:        zzzeek
Date:        2014-03-24 15:22:39
Summary:     - Added some new event mechanics for dialect-level events; the initial
implementation allows an event handler to redefine the specific mechanics
by which an arbitrary dialect invokes execute() or executemany() on a
DBAPI cursor.  The new events, at this point semi-public and experimental,
are in support of some upcoming transaction-related extensions.

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: some profile updates...

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ae7e0a2721b4/
Changeset:   ae7e0a2721b4
Branch:      None
User:        zzzeek
Date:        2014-03-24 02:39:17
Summary:     some profile 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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/39a8e2ed375e/
Changeset:   39a8e2ed375e
Branch:      None
User:        zzzeek
Date:        2014-03-23 00:55:00
Summary:     - Fixed regression from 0.8.3 as a result of :ticket:`2818`
where :meth:`.Query.exists` wouldn't work on a query that only
had a :meth:`.Query.select_from` entry but no other entities.
re: #2818 fixes #2995

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d8aa3d91d7ea/
Changeset:   d8aa3d91d7ea
Branch:      rel_0_8
User:        zzzeek
Date:        2014-03-23 00:55:27
Summary:     - Fixed regression from 0.8.3 as a result of :ticket:`2818`
where :meth:`.Query.exists` wouldn't work on a query that only
had a :meth:`.Query.select_from` entry but no other entities.
re: #2818 fixes #2995

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.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - Fixed a few errant ``u''`` strings that would prevent tests from passing

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5d2bfc4df45b/
Changeset:   5d2bfc4df45b
Branch:      master
User:        zzzeek
Date:        2014-03-22 23:48:59
Summary:     - Fixed a few errant ``u''`` strings that would prevent tests from passing
in Py3.2.  Patch courtesy Arfrever Frehtes Taifersar Arahesis. fixes #2980

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - A major improvement made to the mechanics by which the :class:`.Engine`

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/eed9cfc3ae02/
Changeset:   eed9cfc3ae02
Branch:      master
User:        zzzeek
Date:        2014-03-22 23:45:39
Summary:     - A major improvement made to the mechanics by which the :class:`.Engine`
recycles the connection pool when a "disconnect" condition is detected;
instead of discarding the pool and explicitly closing out connections,
the pool is retained and a "generational" timestamp is updated to
reflect the current time, thereby causing all existing connections
to be recycled when they are next checked out.   This greatly simplifies
the recycle process, removes the need for "waking up" connect attempts
waiting on the old pool and eliminates the race condition that many
immediately-discarded "pool" objects could be created during the
recycle operation. fixes #2985

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - Added new datatype :class:`.oracle.DATE`, which is a subclass of

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/be3c185fd48c/
Changeset:   be3c185fd48c
Branch:      master
User:        zzzeek
Date:        2014-03-22 23:22:17
Summary:     - Added new datatype :class:`.oracle.DATE`, which is a subclass of
:class:`.DateTime`.  As Oracle has no "datetime" type per se,
it instead has only ``DATE``, it is appropriate here that the
``DATE`` type as present in the Oracle dialect be an instance of
:class:`.DateTime`.  This issue doesn't change anything as far as
the behavior of the type, as data conversion is handled by the
DBAPI in any case, however the improved subclass layout will help
the use cases of inspecting types for cross-database compatibility.
Also removed uppercase ``DATETIME`` from the Oracle dialect as this
type isn't functional in that context.  fixes #2987

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.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

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.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/07992a669708/
Changeset:   07992a669708
Branch:      None
User:        borneo
Date:        2014-03-21 14:42:37
Summary:     Fix tag typo in changelog_09
Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/2b1c3d8821b3/
Changeset:   2b1c3d8821b3
Branch:      master
User:        zzzeek
Date:        2014-03-21 14:59:23
Summary:     Merge pull request #81 from tony/patch-2

Fix tag typo in changelog_09
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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a22927b80915/
Changeset:   a22927b80915
Branch:      None
User:        zzzeek
Date:        2014-03-21 03:46:23
Summary:     - reword the paragraph which talks about web framework integration for sessions:

1. fix the typo in the paragraph, fixes #2998
2. as zope-sqlalchemy only provides transaction integration and not session scoping,
dial back the language here as people are probably using scoped_session with pyramid anyway
3. as I'm going to again start recommending people don't cling to flask-sqlalchemy so hard,
take out the word "strongly" from the recommendation.
4. as flask is the only framework I can think of that actually has an explicit SQLAlchemy
layer that handles setting up scoped_session, take out the word "most", now it's "some web frameworks"
(by which it means "only flask...and flask-sqlalchemy is probably not worth using anyway")

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/cb51fe3ef894/
Changeset:   cb51fe3ef894
Branch:      rel_0_8
User:        zzzeek
Date:        2014-03-21 03:51:57
Summary:     - reword the paragraph which talks about web framework integration for sessions:

1. fix the typo in the paragraph, fixes #2998
2. as zope-sqlalchemy only provides transaction integration and not session scoping,
dial back the language here as people are probably using scoped_session with pyramid anyway
3. as I'm going to again start recommending people don't cling to flask-sqlalchemy so hard,
take out the word "strongly" from the recommendation.
4. as flask is the only framework I can think of that actually has an explicit SQLAlchemy
layer that handles setting up scoped_session, take out the word "most", now it's "some web frameworks"
(by which it means "only flask...and flask-sqlalchemy is probably not worth using anyway")

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - The :meth:`.ConnectionEvents.after_cursor_execute` event is now

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2a1a79b6ce53/
Changeset:   2a1a79b6ce53
Branch:      None
User:        zzzeek
Date:        2014-03-19 18:03:44
Summary:     - The :meth:`.ConnectionEvents.after_cursor_execute` event is now
emitted for the "_cursor_execute()" method of :class:`.Connection`;
this is the "quick" executor that is used for things like
when a sequence is executed ahead of an INSERT statement, as well as
for dialect startup checks like unicode returns, charset, etc.
the :meth:`.ConnectionEvents.before_cursor_execute` event was already
invoked here.  The "executemany" flag is now always set to False
here, as this event always corresponds to a single execution.
Previously the flag could be True if we were acting on behalf of
an executemany INSERT statement.

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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/89a8e0d187b8/
Changeset:   89a8e0d187b8
Branch:      None
User:        zzzeek
Date:        2014-03-19 16:47:58
Summary:     fix assertion

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/5f69d83d6c79/
Changeset:   5f69d83d6c79
Branch:      rel_0_8
User:        zzzeek
Date:        2014-03-19 16:48:25
Summary:     fix assertion

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - Fixed bug in mutable extension as well as

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/66d090be9cf0/
Changeset:   66d090be9cf0
Branch:      rel_0_8
User:        zzzeek
Date:        2014-03-19 16:12:24
Summary:     - Fixed bug in mutable extension as well as
:func:`.attributes.flag_modified` where the change event would not be
propagated if the attribute had been reassigned to itself.
fixes #2997

Conflicts:
	lib/sqlalchemy/orm/state.py
	test/orm/test_attributes.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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - Fixed bug in mutable extension as well as

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b9a2b58dd747/
Changeset:   b9a2b58dd747
Branch:      master
User:        zzzeek
Date:        2014-03-19 16:09:38
Summary:     - Fixed bug in mutable extension as well as
:func:`.attributes.flag_modified` where the change event would not be
propagated if the attribute had been reassigned to itself.
fixes #2997

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.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

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.

[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/fb09877270cc/
Changeset:   fb09877270cc
Branch:      None
User:        zzzeek
Date:        2014-03-16 19:50:55
Summary:     - Added support for the not-quite-yet-documented ``insert=True``
flag for :func:`.event.listen` to work with mapper / instance events.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e2214a61e84c/
Changeset:   e2214a61e84c
Branch:      master
User:        zzzeek
Date:        2014-03-16 19:51:06
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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/56e38b8e4e64/
Changeset:   56e38b8e4e64
Branch:      None
User:        zzzeek
Date:        2014-03-15 20:44:29
Summary:     - fairly epic rework of the cascade documentation

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/149584d322da/
Changeset:   149584d322da
Branch:      rel_0_8
User:        zzzeek
Date:        2014-03-15 20:48:52
Summary:     - fairly epic rework of the cascade documentation

Conflicts:
	lib/sqlalchemy/orm/relationships.py

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - correct this to make the intention clear

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6d0f734a3da7/
Changeset:   6d0f734a3da7
Branch:      None
User:        zzzeek
Date:        2014-03-14 01:14:23
Summary:     - correct this to make the intention clear

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.

[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/9c5c12fb230c/
Changeset:   9c5c12fb230c
Branch:      None
User:        zzzeek
Date:        2014-03-14 00:59:10
Summary:     - move some requirements up to the testing module to better support running
SQLA internal tests outside; plus things like savepoints, twophase

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/11003828cb65/
Changeset:   11003828cb65
Branch:      None
User:        zzzeek
Date:        2014-03-14 01:03:48
Summary:     - Added support for literal rendering of boolean values, e.g.
"true" / "false" or "1" / "0".
- added Boolean tests to the test suite

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: comment

[Bitbucket <com...@bi...>]

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2057b86b2ac2/
Changeset:   2057b86b2ac2
Branch:      None
User:        zzzeek
Date:        2014-03-14 00:18:58
Summary:     comment

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.