sqlalchemy-commits — SVN commits logged to this list

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1bc7881171e0/
Changeset:   1bc7881171e0
Branch:      None
User:        Jochen Van de Velde
Date:        2015-05-26 21:27:05+00:00
Summary:     Remove spaces around kwargs in metadata.rst

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/8016ad868acd/
Changeset:   8016ad868acd
Branch:      rel_0_9
User:        Jochen Van de Velde
Date:        2015-05-27 17:54:22+00:00
Summary:     Remove spaces around kwargs in metadata.rst

(cherry picked from commit 1bc7881171e02a80bcdb45191be6c6d83b6f01fd)

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 where known boolean values used by

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a50dcb31b975/
Changeset:   a50dcb31b975
Branch:      None
User:        zzzeek
Date:        2015-05-26 14:56:23+00:00
Summary:     - Fixed bug where known boolean values used by
:func:`.engine_from_config` were not being parsed correctly;
these included ``pool_threadlocal`` and the psycopg2 argument
``use_native_unicode``. fixes #3435
- add legacy_schema_aliasing config parsing for mssql
- move use_native_unicode config arg to the psycopg2 dialect

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: zzzeek: - turn some dials to try to get more log output

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/88f547900276/
Changeset:   88f547900276
Branch:      master
User:        zzzeek
Date:        2015-05-25 18:47:57+00:00
Summary:     - turn some dials to try to get more log 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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - work around RTD issue #1293, take one

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/0618357b84ca/
Changeset:   0618357b84ca
Branch:      master
User:        zzzeek
Date:        2015-05-25 18:34:26+00:00
Summary:     - work around RTD issue #1293, take one

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: zzzeek: - Added a new dialect flag to the MSSQL dialect

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/915791101353/
Changeset:   915791101353
Branch:      None
User:        zzzeek
Date:        2015-05-25 01:02:29+00:00
Summary:     - Added a new dialect flag to the MSSQL dialect
``legacy_schema_aliasing`` which when set to False will disable a
very old and obsolete behavior, that of the compiler's
attempt to turn all schema-qualified table names into alias names,
to work around old and no longer locatable issues where SQL
server could not parse a multi-part identifier name in all
circumstances.   The behavior prevented more
sophisticated statements from working correctly, including those which
use hints, as well as CRUD statements that embed correlated SELECT
statements.  Rather than continue to repair the feature to work
with more complex statements, it's better to just disable it
as it should no longer be needed for any modern SQL server
version.  The flag defaults to True for the 1.0.x series, leaving
current behavior unchanged for this version series.  In the 1.1
series, it will default to False.  For the 1.0 series,
when not set to either value explicitly, a warning is emitted
when a schema-qualified table is first used in a statement, which
suggests that the flag be set to False for all modern SQL Server
versions.
fixes #3424
fixes #3430

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

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

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/96f49085b8dd/
Changeset:   96f49085b8dd
Branch:      None
User:        zzzeek
Date:        2015-05-24 21:07:54+00:00
Summary:     - autopep8

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/0198d9aa5fee/
Changeset:   0198d9aa5fee
Branch:      None
User:        zzzeek
Date:        2015-05-24 21:08:02+00:00
Summary:     - break out binary insert against None, disable for freetds for now

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/0598b789d1c5/
Changeset:   0598b789d1c5
Branch:      None
User:        zzzeek
Date:        2015-05-24 21:09:18+00:00
Summary:     - autopep8

(cherry picked from commit 96f49085b8dd05062b97c4f9c892c071042dad66)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e20c8ce904fd/
Changeset:   e20c8ce904fd
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-24 21:16:51+00:00
Summary:     - break out binary insert against None, disable for freetds for now

(cherry picked from commit 0198d9aa5fee96c7523cc3e827baaba442c0ba02)

- backport no freetds rule

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/1bb9c99ea9f3/
Changeset:   1bb9c99ea9f3
Branch:      None
User:        zzzeek
Date:        2015-05-24 13:49:14+00:00
Summary:     - liberalize list.remove() regexp as recent Pypy versions
format this message differently than cpython

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/c430cdf674e5/
Changeset:   c430cdf674e5
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-24 13:49:46+00:00
Summary:     - liberalize list.remove() regexp as recent Pypy versions
format this message differently than cpython

(cherry picked from commit 1bb9c99ea9f3e36e5d4a9f1d4f21f1d0a252db4a)

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: - fix some tests related to the URL change and try to make

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e9921ad356fe/
Changeset:   e9921ad356fe
Branch:      None
User:        zzzeek
Date:        2015-05-23 13:07:36+00:00
Summary:     - fix some tests related to the URL change and try to make
the URL design a little simpler

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: - Adjustments to the engine plugin hook, such that the

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/04c625467e65/
Changeset:   04c625467e65
Branch:      None
User:        zzzeek
Date:        2015-05-22 17:51:00+00:00
Summary:     - Adjustments to the engine plugin hook, such that the
:meth:`.URL.get_dialect` method will continue to return the
ultimate :class:`.Dialect` object when a dialect plugin is used,
without the need for the caller to be aware of the
:meth:`.Dialect.get_dialect_cls` method.
reference #3379

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/c581b907b3f1/
Changeset:   c581b907b3f1
Branch:      None
User:        zzzeek
Date:        2015-05-22 17:27:09+00:00
Summary:     - document fully how to use autoincrement w/ SQLite including
non-Integer column types, fixes #2075

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/0771e165063c/
Changeset:   0771e165063c
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-22 17:27:53+00:00
Summary:     - document fully how to use autoincrement w/ SQLite including
non-Integer column types, fixes #2075

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/164f2ad2f433/
Changeset:   164f2ad2f433
Branch:      rel_1_0
User:        zzzeek
Date:        2015-05-21 17:43:37+00:00
Summary:     flake8 some tests

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/321f39e3987d/
Changeset:   321f39e3987d
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-21 17:49:11+00:00
Summary:     flake8 some tests

(cherry picked from commit 164f2ad2f433b3d297df709d617a1fc421495921)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/525cc6fe0247/
Changeset:   525cc6fe0247
Branch:      master
User:        zzzeek
Date:        2015-05-21 18:21:01+00:00
Summary:     - Fixed regression in the :mod:`sqlalchemy.ext.mutable` extension
as a result of the bugfix for :ticket:`3167`,
where attribute and validation events are no longer
called within the flush process.  The mutable
extension was relying upon this behavior in the case where a column
level Python-side default were responsible for generating the new value
on INSERT or UPDATE, or when a value were fetched from the RETURNING
clause for "eager defaults" mode.  The new value would not be subject
to any event when populated and the mutable extension could not
establish proper coercion or history listening.  A new event
:meth:`.InstanceEvents.refresh_flush` is added which the mutable
extension now makes use of for this use case.
fixes #3427
- Added new event :meth:`.InstanceEvents.refresh_flush`, invoked
when an INSERT or UPDATE level default value fetched via RETURNING
or Python-side default is invoked within the flush process.  This
is to provide a hook that is no longer present as a result of
:ticket:`3167`, where attribute and validation events are no longer
called within the flush process.
- Added a new semi-public method to :class:`.MutableBase`
:meth:`.MutableBase._get_listen_keys`.  Overriding this method
is needed in the case where a :class:`.MutableBase` subclass needs
events to propagate for attribute keys other than the key to which
the mutable type is associated with, when intercepting the
:meth:`.InstanceEvents.refresh` or
:meth:`.InstanceEvents.refresh_flush` events.  The current example of
this is composites using :class:`.MutableComposite`.

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/9434356da630/
Changeset:   9434356da630
Branch:      None
User:        Pierre Rochard
Date:        2015-05-17 21:28:56+00:00
Summary:     Correcting typo in introspection
Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/cd8f25aa1a83/
Changeset:   cd8f25aa1a83
Branch:      None
User:        zzzeek
Date:        2015-05-21 00:19:22+00:00
Summary:     Merge pull request #173 from PierreRochard/patch-1

Correcting typo in introspection
Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/805f49f6ec79/
Changeset:   805f49f6ec79
Branch:      rel_0_9
User:        Pierre Rochard
Date:        2015-05-21 00:20:07+00:00
Summary:     Correcting typo in introspection
(cherry picked from commit 9434356da63006b3bfbb7833bb62def4cda17189)

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: - pg8000 wants to raise a ProgrammingError for a PK violation

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5ca14954b89a/
Changeset:   5ca14954b89a
Branch:      None
User:        zzzeek
Date:        2015-05-16 01:18:18+00:00
Summary:     - pg8000 wants to raise a ProgrammingError for a PK violation

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: - Added support for the case of the misbehaving DBAPI that has

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d178707ecaeb/
Changeset:   d178707ecaeb
Branch:      None
User:        zzzeek
Date:        2015-05-15 16:38:28+00:00
Summary:     - Added support for the case of the misbehaving DBAPI that has
pep-249 exception names linked to exception classes of an entirely
different name, preventing SQLAlchemy's own exception wrapping from
wrapping the error appropriately.
The SQLAlchemy dialect in use needs to implement a new
accessor :attr:`.DefaultDialect.dbapi_exception_translation_map`
to support this feature; this is implemented now for the py-postgresql
dialect.
fixes #3421

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.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - The "lightweight named tuple" used when a :class:`.Query` returns

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/64c1f2e56888/
Changeset:   64c1f2e56888
Branch:      None
User:        zzzeek
Date:        2015-05-14 23:22:53+00:00
Summary:     - The "lightweight named tuple" used when a :class:`.Query` returns
rows failed to implement ``__slots__`` correctly such that it still
had a ``__dict__``.    This is resolved, but in the extremely
unlikely case someone was assigning values to the returned tuples,
that will no longer work.
fixes #3420

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: zzzeek: - Fixed bug where in the case that a pool checkout event handler is used

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4a0e51e7d2f3/
Changeset:   4a0e51e7d2f3
Branch:      None
User:        zzzeek
Date:        2015-05-14 17:59:04+00:00
Summary:     - Fixed bug where in the case that a pool checkout event handler is used
and the database can no longer be connected towards, that the checkout
handler failure is caught, the attempt to re-acquire the connection
also raises an exception, but the underlying connection record
is not immediately re-checked in before the exception is propagated
outwards, having the effect that the checked-out record does not close
itself until the stack trace it's associated with is garbage collected,
preventing that record from being used for a new checkout until we
leave the scope of the stack trace.   This can lead to confusion
in the specific case of when the number of current stack traces
in memory exceeds the number of connections the pool can return,
as the pool will instead begin to raise errors about no more checkouts
available, rather than attempting a connection again.   The fix
applies a checkin of the record before re-raising.
fixes #3419

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/5c897d9c6a84/
Changeset:   5c897d9c6a84
Branch:      None
User:        zzzeek
Date:        2015-05-08 16:18:07+00:00
Summary:     - start 1.0.5

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/eb1bb84fbc10/
Changeset:   eb1bb84fbc10
Branch:      None
User:        zzzeek
Date:        2015-05-08 16:37:55+00:00
Summary:     - Added official support for a CTE used by the SELECT present
inside of :meth:`.Insert.from_select`.  This behavior worked
accidentally up until 0.9.9, when it no longer worked due to
unrelated changes as part of :ticket:`3248`.   Note that this
is the rendering of the WITH clause after the INSERT, before the
SELECT; the full functionality of CTEs rendered at the top
level of INSERT, UPDATE, DELETE is a new feature targeted for a
later release.
fixes #3418

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/87c605e3dc8b/
Changeset:   87c605e3dc8b
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-08 16:42:36+00:00
Summary:     - Added official support for a CTE used by the SELECT present
inside of :meth:`.Insert.from_select`.  This behavior worked
accidentally up until 0.9.9, when it no longer worked due to
unrelated changes as part of :ticket:`3248`.   Note that this
is the rendering of the WITH clause after the INSERT, before the
SELECT; the full functionality of CTEs rendered at the top
level of INSERT, UPDATE, DELETE is a new feature targeted for a
later release.
fixes #3418

(cherry picked from commit eb1bb84fbc10c801c7269a3d38c9e0235327857e)

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: 1.0.4

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/148924821bf8/
Changeset:   148924821bf8
Branch:      master
User:        zzzeek
Date:        2015-05-08 00:51:09+00:00
Summary:     1.0.4

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/6d7901fa7d3f/
Changeset:   6d7901fa7d3f
Branch:      None
User:        zzzeek
Date:        2015-05-07 20:19:08+00:00
Summary:     - plead with RTD to please please use the correct version

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/3c7064201226/
Changeset:   3c7064201226
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 20:19:32+00:00
Summary:     - plead with RTD to please please use the correct version

(cherry picked from commit 6d7901fa7d3feb5c7894e31a48d249b445557f20)

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/6b55842eef3a/
Changeset:   6b55842eef3a
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 20:05:48+00:00
Summary:     RTD doesn't seem to want to refresh on a git tag so go back to using
release numbers

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/ed73a95db6b5/
Changeset:   ed73a95db6b5
Branch:      None
User:        zzzeek
Date:        2015-05-07 20:06:11+00:00
Summary:     RTD doesn't seem to want to refresh on a git tag so go back to using
release numbers

(cherry picked from commit 6b55842eef3a243d275bdd5630c1fe62d98e8371)

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/4f31db82100b/
Changeset:   4f31db82100b
Branch:      None
User:        zzzeek
Date:        2015-05-07 17:47:38+00:00
Summary:     - re-tag zzzeeksphinx w/ new version supporting sphinx 1.3

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/25664b06f9fd/
Changeset:   25664b06f9fd
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 17:48:01+00:00
Summary:     - re-tag zzzeeksphinx w/ new version supporting sphinx 1.3

(cherry picked from commit 4f31db82100bee20284d8e9273ac9c6d147a32e3)

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/ae4c2b6cbee0/
Changeset:   ae4c2b6cbee0
Branch:      None
User:        zzzeek
Date:        2015-05-07 16:34:38+00:00
Summary:     - bump zs version due to not yet diagnosed error

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/644b75c8a6de/
Changeset:   644b75c8a6de
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-07 16:34:59+00:00
Summary:     - bump zs version due to not yet diagnosed error

(cherry picked from commit ae4c2b6cbee0f993b3937237411df7fb8e66592d)

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: - fix for py3k

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/633a61d978ba/
Changeset:   633a61d978ba
Branch:      None
User:        zzzeek
Date:        2015-05-07 13:50:37+00:00
Summary:     - fix for py3k

Affected #:  1 file

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - Fixed unexpected-use regression where in the odd case that the

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1b120563905e/
Changeset:   1b120563905e
Branch:      None
User:        zzzeek
Date:        2015-05-06 21:07:24+00:00
Summary:     - Fixed unexpected-use regression where in the odd case that the
primaryjoin of a relationship involved comparison to an unhashable
type such as an HSTORE, lazy loads would fail due to a hash-oriented
check on the statement parameters, modified in 1.0 as a result of
:ticket:`3061` to use hashing and modified in :ticket:`3368`
to occur in cases more common than "load on pending".
The values are now checked for the ``__hash__`` attribute beforehand.
fixes #3416

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: - appease oracle's anger (no sequence defined for these PKs)

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5c852409219e/
Changeset:   5c852409219e
Branch:      None
User:        zzzeek
Date:        2015-05-05 21:01:13+00:00
Summary:     - appease oracle's anger (no sequence defined for these PKs)

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.