sqlalchemy-commits

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/cc3dba01db03/
Changeset:   cc3dba01db03
Branch:      None
User:        zzzeek
Date:        2014-09-16 22:20:22
Summary:     - raise from cause here to preserve stack trace

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/f6f5fc7f17d7/
Changeset:   f6f5fc7f17d7
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-16 22:20:50
Summary:     - raise from cause here to preserve stack trace

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/a985f84ed622/
Changeset:   a985f84ed622
Branch:      None
User:        zzzeek
Date:        2014-09-16 23:40:06
Summary:     - Fixed the version string detection in the pymssql dialect to
work with Microsoft SQL Azure, which changes the word "SQL Server"
to "SQL Azure".
fixes #3151

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/0477501eddee/
Changeset:   0477501eddee
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-16 23:41:07
Summary:     - Fixed the version string detection in the pymssql dialect to
work with Microsoft SQL Azure, which changes the word "SQL Server"
to "SQL Azure".
fixes #3151

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/9ae4db27b993/
Changeset:   9ae4db27b993
Branch:      None
User:        zzzeek
Date:        2014-09-18 19:24:40+00:00
Summary:     - Fixed bug that affected many classes of event, particularly
ORM events but also engine events, where the usual logic of
"de duplicating" a redundant call to :func:`.event.listen`
with the same arguments would fail, for those events where the
listener function is wrapped.  An assertion would be hit within
registry.py.  This assertion has now been integrated into the
deduplication check, with the added bonus of a simpler means
of checking deduplication across the board.
fixes #3199

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/322e2568fb37/
Changeset:   322e2568fb37
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-18 19:27:43+00:00
Summary:     - Fixed bug that affected many classes of event, particularly
ORM events but also engine events, where the usual logic of
"de duplicating" a redundant call to :func:`.event.listen`
with the same arguments would fail, for those events where the
listener function is wrapped.  An assertion would be hit within
registry.py.  This assertion has now been integrated into the
deduplication check, with the added bonus of a simpler means
of checking deduplication across the board.
fixes #3199

Conflicts:
	lib/sqlalchemy/event/registry.py
	test/base/test_events.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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c7ec21b29e92/
Changeset:   c7ec21b29e92
Branch:      None
User:        zzzeek
Date:        2014-09-18 19:42:27+00:00
Summary:     - Fixed an unlikely race condition observed in some exotic end-user
setups, where the attempt to check for "duplicate class name" in
declarative would hit upon a not-totally-cleaned-up weak reference
related to some other class being removed; the check here now ensures
the weakref still references an object before calling upon it further.
fixes #3208

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/80cd802296af/
Changeset:   80cd802296af
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-18 19:42:51+00:00
Summary:     - Fixed an unlikely race condition observed in some exotic end-user
setups, where the attempt to check for "duplicate class name" in
declarative would hit upon a not-totally-cleaned-up weak reference
related to some other class being removed; the check here now ensures
the weakref still references an object before calling upon it further.
fixes #3208

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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b36cdefba273/
Changeset:   b36cdefba273
Branch:      None
User:        zzzeek
Date:        2014-09-18 21:49:07+00:00
Summary:     - Fixed bug that affected generally the same classes of event
as that of :ticket:`3199`, when the ``named=True`` parameter
would be used.  Some events would fail to register, and others
would not invoke the event arguments correctly, generally in the
case of when an event was "wrapped" for adaption in some other way.
The "named" mechanics have been rearranged to not interfere with
the argument signature expected by internal wrapper functions.
fixes #3197

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/912ebaa8b02f/
Changeset:   912ebaa8b02f
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-18 21:54:42+00:00
Summary:     - Fixed bug that affected generally the same classes of event
as that of :ticket:`3199`, when the ``named=True`` parameter
would be used.  Some events would fail to register, and others
would not invoke the event arguments correctly, generally in the
case of when an event was "wrapped" for adaption in some other way.
The "named" mechanics have been rearranged to not interfere with
the argument signature expected by internal wrapper functions.
fixes #3197

Conflicts:
	test/base/test_events.py
	test/orm/test_attributes.py
	test/orm/test_events.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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f458ef84569c/
Changeset:   f458ef84569c
Branch:      None
User:        zzzeek
Date:        2014-09-19 16:41:07+00:00
Summary:     - these tests don't test anything in SQLAlchemy - from our perpsective,
we need to be in transactions (tested elsewhere) and we need to
emit the correct FOR UPDATE strings (tested elsewhere).  There's nothing
in SQLA to be tested as far as validating that for update causes exceptions
or not, and these tests frequently fail as they are timing sensitive.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/863dbfca15da/
Changeset:   863dbfca15da
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-19 16:42:03+00:00
Summary:     - these tests don't test anything in SQLAlchemy - from our perpsective,
we need to be in transactions (tested elsewhere) and we need to
emit the correct FOR UPDATE strings (tested elsewhere).  There's nothing
in SQLA to be tested as far as validating that for update causes exceptions
or not, and these tests frequently fail as they are timing sensitive.

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/1dacbb25f86f/
Changeset:   1dacbb25f86f
Branch:      None
User:        zzzeek
Date:        2014-09-23 02:22:09+00:00
Summary:     pep8/flake8

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/5508388f0325/
Changeset:   5508388f0325
Branch:      None
User:        zzzeek
Date:        2014-09-23 03:00:45+00:00
Summary:     - The :mod:`sqlalchemy.ext.automap` extension will now set
``cascade="all, delete-orphan"`` automatically on a one-to-many
relationship/backref where the foreign key is detected as containing
one or more non-nullable columns.  This argument is present in the
keywords passed to :func:`.automap.generate_relationship` in this
case and can still be overridden.  Additionally, if the
:class:`.ForeignKeyConstraint` specifies ``ondelete="CASCADE"``
for a non-nullable or ``ondelete="SET NULL"`` for a nullable set
of columns, the argument ``passive_deletes=True`` is also added to the
relationship.  Note that not all backends support reflection of
ondelete, but backends that do include Postgresql and MySQL.
fixes #3210

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/360477cc3af8/
Changeset:   360477cc3af8
Branch:      None
User:        zzzeek
Date:        2014-09-23 17:25:22+00:00
Summary:     - flake8 all of test/ext/declarative

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/fca831552f6c/
Changeset:   fca831552f6c
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-23 17:25:38+00:00
Summary:     - flake8 all of test/ext/declarative

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: 2 new changesets

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/42837f4bca6a/
Changeset:   42837f4bca6a
Branch:      None
User:        zzzeek
Date:        2014-09-24 18:49:30+00:00
Summary:     - clarify documentation on exists() that it is preferred to be in the
WHERE clause.  fixes #3212

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/98f457a5e2f8/
Changeset:   98f457a5e2f8
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-24 18:49:59+00:00
Summary:     - clarify documentation on exists() that it is preferred to be in the
WHERE clause.  fixes #3212

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/3b79eafdbf3b/
Changeset:   3b79eafdbf3b
Branch:      None
User:        zzzeek
Date:        2014-09-25 00:53:29+00:00
Summary:     - simplify.  make the base declared_attr memoized.

Affected #:  7 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/22414000028b/
Changeset:   22414000028b
Branch:      ticket_3150
User:        zzzeek
Date:        2014-09-25 01:09:16+00:00
Summary:     - clean up imports

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/08f96c8bc59f/
Changeset:   08f96c8bc59f
Branch:      None
User:        zzzeek
Date:        2014-09-25 20:54:54+00:00
Summary:     - try to simplify. do away with after_mapping.

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1638c31e1440/
Changeset:   1638c31e1440
Branch:      ticket_3150
User:        zzzeek
Date:        2014-09-25 21:28:01+00:00
Summary:     - lets create column copies first and fix this problem completely.
now we don't need after_mapping at all.

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: 2 new changesets

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b1a956d4210c/
Changeset:   b1a956d4210c
Branch:      None
User:        zzzeek
Date:        2014-09-26 16:50:18+00:00
Summary:     - add explicit warning re: polymorphic_on, cascading is not supported
at this time.  ref #3214

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9967c8a9104e/
Changeset:   9967c8a9104e
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-26 16:51:04+00:00
Summary:     - add explicit warning re: polymorphic_on, cascading is not supported
at this time.  ref #3214

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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b6496ba3d28d/
Changeset:   b6496ba3d28d
Branch:      None
User:        zzzeek
Date:        2014-09-29 21:33:53+00:00
Summary:     - A revisit to this issue first patched in 0.9.5, apparently
psycopg2's ``.closed`` accessor is not as reliable as we assumed,
so we have added an explicit check for the exception messages
"SSL SYSCALL error: Bad file descriptor" and
"SSL SYSCALL error: EOF detected" when detecting an
is-disconnect scenario.   We will continue to consult psycopg2's
connection.closed as a first check.
fixes #3021

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/2f4db5307ce0/
Changeset:   2f4db5307ce0
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-29 21:34:15+00:00
Summary:     - A revisit to this issue first patched in 0.9.5, apparently
psycopg2's ``.closed`` accessor is not as reliable as we assumed,
so we have added an explicit check for the exception messages
"SSL SYSCALL error: Bad file descriptor" and
"SSL SYSCALL error: EOF detected" when detecting an
is-disconnect scenario.   We will continue to consult psycopg2's
connection.closed as a first check.
fixes #3021

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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4da020dae324/
Changeset:   4da020dae324
Branch:      None
User:        zzzeek
Date:        2014-09-29 22:09:25+00:00
Summary:     - rework tests for attached databases into individual tests,
test both memory and file-based
- When selecting from a UNION using an attached database file,
the pysqlite driver reports column names in cursor.description
as 'dbname.tablename.colname', instead of 'tablename.colname' as
it normally does for a UNION (note that it's supposed to just be
'colname' for both, but we work around it).  The column translation
logic here has been adjusted to retrieve the rightmost token, rather
than the second token, so it works in both cases.   Workaround
courtesy Tony Roberts.
fixes #3211

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/49f4d98c04f2/
Changeset:   49f4d98c04f2
Branch:      rel_0_9
User:        zzzeek
Date:        2014-09-29 22:10:32+00:00
Summary:     - rework tests for attached databases into individual tests,
test both memory and file-based
- When selecting from a UNION using an attached database file,
the pysqlite driver reports column names in cursor.description
as 'dbname.tablename.colname', instead of 'tablename.colname' as
it normally does for a UNION (note that it's supposed to just be
'colname' for both, but we work around it).  The column translation
logic here has been adjusted to retrieve the rightmost token, rather
than the second token, so it works in both cases.   Workaround
courtesy Tony Roberts.
fixes #3211

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/119674dd250d/
Changeset:   119674dd250d
Branch:      None
User:        zzzeek
Date:        2014-10-06 22:23:42+00:00
Summary:     - The execution options passed to an :class:`.Engine` either via
:paramref:`.create_engine.execution_options` or
:meth:`.Engine.update_execution_options` are not passed to the
special :class:`.Connection` used to initialize the dialect
within the "first connect" event; dialects will usually
perform their own queries in this phase, and none of the
current available  options should be applied here.  In
particular, the "autocommit" option was causing an attempt to
autocommit within this initial connect which would fail with
an AttributeError due to the non-standard state of the
:class:`.Connection`.
fixes #3200

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/96e17a14c5f2/
Changeset:   96e17a14c5f2
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-06 22:24:11+00:00
Summary:     - The execution options passed to an :class:`.Engine` either via
:paramref:`.create_engine.execution_options` or
:meth:`.Engine.update_execution_options` are not passed to the
special :class:`.Connection` used to initialize the dialect
within the "first connect" event; dialects will usually
perform their own queries in this phase, and none of the
current available  options should be applied here.  In
particular, the "autocommit" option was causing an attempt to
autocommit within this initial connect which would fail with
an AttributeError due to the non-standard state of the
:class:`.Connection`.
fixes #3200

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/5a10b6a455f9/
Changeset:   5a10b6a455f9
Branch:      None
User:        zzzeek
Date:        2014-10-06 22:33:05+00:00
Summary:     - Fixed "'NoneType' object has no attribute 'concrete'" error
when using :class:`.AbstractConcreteBase` in conjunction with
a subclass that declares ``__abstract__``.
fixes #3185

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/24cd39de0fc1/
Changeset:   24cd39de0fc1
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-06 22:34:16+00:00
Summary:     - Fixed "'NoneType' object has no attribute 'concrete'" error
when using :class:`.AbstractConcreteBase` in conjunction with
a subclass that declares ``__abstract__``.
fixes #3185

Conflicts:
	test/ext/declarative/test_inheritance.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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2885f78e4e20/
Changeset:   2885f78e4e20
Branch:      None
User:        zzzeek
Date:        2014-10-07 16:43:27+00:00
Summary:     - adjustment for ref #3200 as we need an immutabledict() here so
that union() can be called, in the case of a dialect that uses
execution options inside of initialize() (e.g. oursql)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ce3f986a0e49/
Changeset:   ce3f986a0e49
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-07 16:45:24+00:00
Summary:     - adjustment for ref #3200 as we need an immutabledict() here so
that union() can be called, in the case of a dialect that uses
execution options inside of initialize() (e.g. oursql)

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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c55d10940b19/
Changeset:   c55d10940b19
Branch:      None
User:        zzzeek
Date:        2014-10-07 18:06:46+00:00
Summary:     - clean up unicode docs and clarify that client_encoding
at the engine level is not the same thing as at the connect args
level.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/4f16700596cf/
Changeset:   4f16700596cf
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-07 18:07:27+00:00
Summary:     - clean up unicode docs and clarify that client_encoding
at the engine level is not the same thing as at the connect args
level.

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/3a6cdff88429/
Changeset:   3a6cdff88429
Branch:      None
User:        zzzeek
Date:        2014-10-10 19:31:07+00:00
Summary:     - apply patches to correct for + sign in with_hint() docs,
fixes #3036

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/702166dc1abf/
Changeset:   702166dc1abf
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-10 19:31:32+00:00
Summary:     - apply patches to correct for + sign in with_hint() docs,
fixes #3036

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/ff34c480dfd2/
Changeset:   ff34c480dfd2
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-13 17:10:15+00:00
Summary:     0.9.8

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/09e2a15a8052/
Changeset:   09e2a15a8052
Branch:      None
User:        zzzeek
Date:        2014-10-13 17:17:24+00:00
Summary:     - merge 0.9.8 release date

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/1e5ffa029a2b/
Changeset:   1e5ffa029a2b
Branch:      None
User:        zzzeek
Date:        2014-10-14 16:07:38+00:00
Summary:     - move BindTest into orm/test_binds

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6de1a878702b/
Changeset:   6de1a878702b
Branch:      None
User:        zzzeek
Date:        2014-10-14 18:04:17+00:00
Summary:     - Improvements to the mechanism used by :class:`.Session` to locate
"binds" (e.g. engines to use), such engines can be associated with
mixin classes, concrete subclasses, as well as a wider variety
of table metadata such as joined inheritance tables.
fixes #3035

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: 2 new changesets

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a02664869c09/
Changeset:   a02664869c09
Branch:      None
User:        zzzeek
Date:        2014-10-16 17:30:51+00:00
Summary:     - fix imports
- pep8

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/61a4a89d993e/
Changeset:   61a4a89d993e
Branch:      None
User:        zzzeek
Date:        2014-10-16 18:36:56+00:00
Summary:     - The :meth:`.Query.update` method will now convert string key
names in the given dictionary of values into mapped attribute names
against the mapped class being updated.  Previously, string names
were taken in directly and passed to the core update statement without
any means to resolve against the mapped entity.  Support for synonyms
and hybrid attributes as the subject attributes of
:meth:`.Query.update` are also supported.
fixes #3228

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: 2 new changesets

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2924f8685c1d/
Changeset:   2924f8685c1d
Branch:      None
User:        zzzeek
Date:        2014-10-17 23:29:32+00:00
Summary:     pep8

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/6f40eb37cbdc/
Changeset:   6f40eb37cbdc
Branch:      None
User:        zzzeek
Date:        2014-10-17 23:37:45+00:00
Summary:     - Exception messages have been spiffed up a bit.  The SQL statement
and parameters are not displayed if None, reducing confusion for
error messages that weren't related to a statement.  The full
module and classname for the DBAPI-level exception is displayed,
making it clear that this is a wrapped DBAPI exception.  The
statement and parameters themselves are bounded within a bracketed
sections to better isolate them from the error message and from
each other.
fixes #3172

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: 2 new changesets

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/38bc8098419d/
Changeset:   38bc8098419d
Branch:      None
User:        zzzeek
Date:        2014-10-19 20:53:45+00:00
Summary:     - Fixed bug where :meth:`.Session.expunge` would not fully detach
the given object if the object had been subject to a delete
operation that was flushed, but not committed.  This would also
affect related operations like :func:`.make_transient`.
fixes #3139

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/de8754faf9a1/
Changeset:   de8754faf9a1
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-19 20:56:18+00:00
Summary:     - repair documenation for object_session(), returns None if no
session, and refer to InstanceState.session.  Add note about
objects that are deleted within an ongoing transaction.

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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c5fa20fb2a85/
Changeset:   c5fa20fb2a85
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-23 04:42:43+00:00
Summary:     - Fixed bug where the ON clause for :meth:`.Query.join`,
and :meth:`.Query.outerjoin` to a single-inheritance subclass
using ``of_type()`` would not render the "single table criteria" in
the ON clause if the ``from_joinpoint=True`` flag were set.
fixes #3232

Conflicts:
	test/orm/inheritance/test_single.py

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/47d316ec665e/
Changeset:   47d316ec665e
Branch:      None
User:        zzzeek
Date:        2014-10-23 04:43:11+00:00
Summary:     - Fixed bug where the ON clause for :meth:`.Query.join`,
and :meth:`.Query.outerjoin` to a single-inheritance subclass
using ``of_type()`` would not render the "single table criteria" in
the ON clause if the ``from_joinpoint=True`` flag were set.
fixes #3232

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.