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/e57bf7961692/
Changeset:   e57bf7961692
Branch:      None
User:        zzzeek
Date:        2015-12-09 23:15:25+00:00
Summary:     - Fixed issue within the :meth:`.Insert.from_select` construct whereby
the :class:`.Select` construct would have its ``._raw_columns``
collection mutated in-place when compiling the :class:`.Insert`
construct, when the target :class:`.Table` has Python-side defaults.
The :class:`.Select` construct would compile standalone with the
erroneous column present subsequent to compilation of the
:class:`.Insert`, and the the :class:`.Insert` statement itself would
fail on a second compile attempt due to duplicate bound parameters.
fixes #3603

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6d44b0126301/
Changeset:   6d44b0126301
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-09 23:15:57+00:00
Summary:     - Fixed issue within the :meth:`.Insert.from_select` construct whereby
the :class:`.Select` construct would have its ``._raw_columns``
collection mutated in-place when compiling the :class:`.Insert`
construct, when the target :class:`.Table` has Python-side defaults.
The :class:`.Select` construct would compile standalone with the
erroneous column present subsequent to compilation of the
:class:`.Insert`, and the the :class:`.Insert` statement itself would
fail on a second compile attempt due to duplicate bound parameters.
fixes #3603

(cherry picked from commit e57bf796169282f69187f50665f5ea233c2c9ab7)

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/67b22cee3ab2/
Changeset:   67b22cee3ab2
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-08 18:49:56+00:00
Summary:     - fix changelog for #3602
- add version switch for backend fsp test

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/f4a1129e79e0/
Changeset:   f4a1129e79e0
Branch:      None
User:        zzzeek
Date:        2015-12-08 18:50:25+00:00
Summary:     - fix changelog for #3602
- add version switch for backend fsp test

(cherry picked from commit 67b22cee3ab2c17b61100f1ccd69081082c0f074)

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/7df4054b04ed/
Changeset:   7df4054b04ed
Branch:      None
User:        zzzeek
Date:        2015-12-08 15:40:45+00:00
Summary:     - make this DROP conditional, attempting to isolate why jenkins has
an issue with just one test

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/7574762aa085/
Changeset:   7574762aa085
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-08 15:42:44+00:00
Summary:     - make this DROP conditional, attempting to isolate why jenkins has
an issue with just one test

(cherry picked from commit 7df4054b04ed54504be2c2ab8a83721748130780)

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

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

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d7eae8c95ca8/
Changeset:   d7eae8c95ca8
Branch:      None
User:        zzzeek
Date:        2015-12-07 22:09:11+00:00
Summary:     - flake8 test_reflection and rework the type-based tests into
individual categories w/ modernized fixtures, assert attributes
within type objects.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/3f42743d6aa1/
Changeset:   3f42743d6aa1
Branch:      None
User:        zzzeek
Date:        2015-12-07 22:24:09+00:00
Summary:     - Fixed bug in MySQL reflection where the "fractional sections portion"
of the :class:`.mysql.DATETIME`, :class:`.mysql.TIMESTAMP` and
:class:`.mysql.TIME` types would be incorrectly placed into the
``timestamp`` attribute, which is unused by MySQL, instead of the
``fsp`` attribute.
fixes #3602

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c18ff4e404af/
Changeset:   c18ff4e404af
Branch:      None
User:        zzzeek
Date:        2015-12-07 22:25:23+00:00
Summary:     - flake8 test_reflection and rework the type-based tests into
individual categories w/ modernized fixtures, assert attributes
within type objects.

(cherry picked from commit d7eae8c95ca8c5963fc78fc997ed0f2da76aed31)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/f3137aa45998/
Changeset:   f3137aa45998
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-07 22:25:27+00:00
Summary:     - Fixed bug in MySQL reflection where the "fractional sections portion"
of the :class:`.mysql.DATETIME`, :class:`.mysql.TIMESTAMP` and
:class:`.mysql.TIME` types would be incorrectly placed into the
``timestamp`` attribute, which is unused by MySQL, instead of the
``fsp`` attribute.
fixes #3602

(cherry picked from commit 3f42743d6aa1326a80a0ed720a92266aa5fbf209)

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/8fa62d652b8d/
Changeset:   8fa62d652b8d
Branch:      None
User:        zzzeek
Date:        2015-12-07 17:36:36+00:00
Summary:     - write a real inline documentation section for from_self(),
building on the example of query.join().  Ideally all the methods
in Query would have this kind of thing.  fixes #3544

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/fb16fe1b1942/
Changeset:   fb16fe1b1942
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-07 17:37:25+00:00
Summary:     - write a real inline documentation section for from_self(),
building on the example of query.join().  Ideally all the methods
in Query would have this kind of thing.  fixes #3544

(cherry picked from commit 8fa62d652b8d1834e23ba36e56c7bd711cc37e37)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/2506d7202f49/
Changeset:   2506d7202f49
Branch:      rel_0_9
User:        zzzeek
Date:        2015-12-07 17:37:29+00:00
Summary:     - write a real inline documentation section for from_self(),
building on the example of query.join().  Ideally all the methods
in Query would have this kind of thing.  fixes #3544

(cherry picked from commit 8fa62d652b8d1834e23ba36e56c7bd711cc37e37)

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/077f26af5f6f/
Changeset:   077f26af5f6f
Branch:      None
User:        zzzeek
Date:        2015-12-05 22:17:40+00:00
Summary:     - and NLS_LANG....

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/03ca213fe913/
Changeset:   03ca213fe913
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-05 22:17:55+00:00
Summary:     - and NLS_LANG....

(cherry picked from commit 077f26af5f6fefdc98f6720ab5e02b0fad6eff7a)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/e8d6cc207b05/
Changeset:   e8d6cc207b05
Branch:      rel_0_9
User:        zzzeek
Date:        2015-12-05 22:17:58+00:00
Summary:     - and NLS_LANG....

(cherry picked from commit 077f26af5f6fefdc98f6720ab5e02b0fad6eff7a)

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/0fb6b626dd36/
Changeset:   0fb6b626dd36
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-05 21:57:55+00:00
Summary:     - add ORACLE_HOME to passenv allowing oracle to work w/ tox 2.0

(cherry picked from commit 7f423e875669ee549b1f53f90d2db340b6c957cd)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/a627573510a5/
Changeset:   a627573510a5
Branch:      rel_0_9
User:        zzzeek
Date:        2015-12-05 21:59:03+00:00
Summary:     - add ORACLE_HOME to passenv allowing oracle to work w/ tox 2.0

(cherry picked from commit 7f423e875669ee549b1f53f90d2db340b6c957cd)

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: - add ORACLE_HOME to passenv allowing oracle to work w/ tox 2.0

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/7f423e875669/
Changeset:   7f423e875669
Branch:      master
User:        zzzeek
Date:        2015-12-05 21:56:53+00:00
Summary:     - add ORACLE_HOME to passenv allowing oracle to work w/ tox 2.0

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 loading.py merge_result for new _merge() argument

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/012f3852bf03/
Changeset:   012f3852bf03
Branch:      None
User:        zzzeek
Date:        2015-12-04 22:31:47+00:00
Summary:     - fix loading.py merge_result for new _merge() argument

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:`.Session.merge` method now tracks pending objects by

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/3ec9b9f6b601/
Changeset:   3ec9b9f6b601
Branch:      None
User:        zzzeek
Date:        2015-12-04 16:52:16+00:00
Summary:     - The :meth:`.Session.merge` method now tracks pending objects by
primary key before emitting an INSERT, and merges distinct objects with
duplicate primary keys together as they are encountered, which is
essentially semi-deterministic at best.   This behavior
matches what happens already with persistent objects.
fixes #3601

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/935bc34dc50d/
Changeset:   935bc34dc50d
Branch:      None
User:        zzzeek
Date:        2015-12-02 17:13:57+00:00
Summary:     - Fixed issue where post_update on a many-to-one relationship would
fail to emit an UPDATE in the case where the attribute were set to
None and not previously loaded.
fixes #3599

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/74fcb4b86719/
Changeset:   74fcb4b86719
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-02 17:14:18+00:00
Summary:     - Fixed issue where post_update on a many-to-one relationship would
fail to emit an UPDATE in the case where the attribute were set to
None and not previously loaded.
fixes #3599

(cherry picked from commit 935bc34dc50d5e4bdf181a8287d6e4cdbde073d0)

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/9695faf32981/
Changeset:   9695faf32981
Branch:      None
User:        zzzeek
Date:        2015-12-02 00:03:03+00:00
Summary:     - Fixed bug where CREATE TABLE with a no-column table, but a constraint
such as a CHECK constraint would render an erroneous comma in the
definition; this scenario can occur such as with a Postgresql
INHERITS table that has no columns of its own.
fixes #3598

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7b5fd86a42cf/
Changeset:   7b5fd86a42cf
Branch:      rel_1_0
User:        zzzeek
Date:        2015-12-02 00:04:48+00:00
Summary:     - Fixed bug where CREATE TABLE with a no-column table, but a constraint
such as a CHECK constraint would render an erroneous comma in the
definition; this scenario can occur such as with a Postgresql
INHERITS table that has no columns of its own.
fixes #3598

(cherry picked from commit 9695faf32981406b12a6468b98d5c9b673f8e219)

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/ab6946769742/
Changeset:   ab6946769742
Branch:      None
User:        zzzeek
Date:        2015-11-30 18:15:40+00:00
Summary:     - Added the error "20006: Write to the server failed" to the list
of disconnect errors for the pymssql driver, as this has been observed
to render a connection unusable.
fixes #3585

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b30390bfb3a6/
Changeset:   b30390bfb3a6
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 18:16:11+00:00
Summary:     - Added the error "20006: Write to the server failed" to the list
of disconnect errors for the pymssql driver, as this has been observed
to render a connection unusable.
fixes #3585

(cherry picked from commit ab6946769742602e40fb9ed9dde5f642885d1906)

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

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

5 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/fd47fea6fbb1/
Changeset:   fd47fea6fbb1
Branch:      None
User:        _diana_
Date:        2015-11-24 18:58:50+00:00
Summary:     - Postgres: Do not prefix table with schema in: "FOR UPDATE of <table>"

For example, this query:

    SELECT s1.users.name FROM s1.users FOR UPDATE OF s1.users

should actually be:

    SELECT s1.users.name FROM s1.users FOR UPDATE OF users

fixes #3573

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9c2c2475637d/
Changeset:   9c2c2475637d
Branch:      None
User:        zzzeek
Date:        2015-11-30 18:02:39+00:00
Summary:     Merge remote-tracking branch 'origin/pr/216'

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/f4cb3f8cacaf/
Changeset:   f4cb3f8cacaf
Branch:      None
User:        zzzeek
Date:        2015-11-30 18:06:11+00:00
Summary:     - changelog for #3573, fixes #3573

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/104cfe149ab7/
Changeset:   104cfe149ab7
Branch:      None
User:        _diana_
Date:        2015-11-30 18:06:39+00:00
Summary:     - Postgres: Do not prefix table with schema in: "FOR UPDATE of <table>"

For example, this query:

    SELECT s1.users.name FROM s1.users FOR UPDATE OF s1.users

should actually be:

    SELECT s1.users.name FROM s1.users FOR UPDATE OF users

fixes #3573

(cherry picked from commit fd47fea6fbb11ee84b7eea5772f40855703ebe47)

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/fb22efc9de8d/
Changeset:   fb22efc9de8d
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 18:06:43+00:00
Summary:     - changelog for #3573, fixes #3573

(cherry picked from commit f4cb3f8cacaf96f064c2c7e4c1e579c7cf6544da)

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

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

5 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/0921a6abbc82/
Changeset:   0921a6abbc82
Branch:      None
User:        aisch
Date:        2015-11-23 18:22:50+00:00
Summary:     fix postgresql exclude contraint to check when= against None rather than __bool__ eval

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/a09fc9740d04/
Changeset:   a09fc9740d04
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:57:47+00:00
Summary:     Merge remote-tracking branch 'origin/pr/215'

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c3fbfa8257dd/
Changeset:   c3fbfa8257dd
Branch:      None
User:        zzzeek
Date:        2015-11-30 18:01:07+00:00
Summary:     - changelog for pullreq github:215

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/bb2b486de557/
Changeset:   bb2b486de557
Branch:      None
User:        aisch
Date:        2015-11-30 18:01:33+00:00
Summary:     fix postgresql exclude contraint to check when= against None rather than __bool__ eval

(cherry picked from commit 0921a6abbc8246c57f447af7a6ac240778127fae)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c392ba1de775/
Changeset:   c392ba1de775
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 18:01:38+00:00
Summary:     - changelog for pullreq github:215

(cherry picked from commit c3fbfa8257dd198f1020166ce3c94556984abed0)

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/0438065a20f3/
Changeset:   0438065a20f3
Branch:      None
User:        sigmaris
Date:        2015-11-28 15:21:11+00:00
Summary:     Fix a typo in the disconnect handling code example
Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/954aafa0645f/
Changeset:   954aafa0645f
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:55:26+00:00
Summary:     Merge remote-tracking branch 'origin/pr/217'

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/66704ad47ab9/
Changeset:   66704ad47ab9
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 17:55:38+00:00
Summary:     Merge remote-tracking branch 'origin/pr/217'

(cherry picked from commit 954aafa0645f6e1ccbcfdc358a9f2930a24461a4)

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

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

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/11e190ef079e/
Changeset:   11e190ef079e
Branch:      None
User:        jeffwidman
Date:        2015-11-17 02:47:29+00:00
Summary:     Fix typo: wtihin --> within
Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/38e043a475db/
Changeset:   38e043a475db
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:53:56+00:00
Summary:     Merge remote-tracking branch 'origin/pr/214'

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/b552a75a5248/
Changeset:   b552a75a5248
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 17:54:08+00:00
Summary:     Merge remote-tracking branch 'origin/pr/214'

(cherry picked from commit 38e043a475db210143c46588fca70838c9c47c8a)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/723c96f7f5db/
Changeset:   723c96f7f5db
Branch:      rel_0_9
User:        zzzeek
Date:        2015-11-30 17:54:18+00:00
Summary:     Merge remote-tracking branch 'origin/pr/214'

(cherry picked from commit 38e043a475db210143c46588fca70838c9c47c8a)

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

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

6 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/58f73d227839/
Changeset:   58f73d227839
Branch:      None
User:        Nils Philippsen
Date:        2015-11-25 15:03:59+00:00
Summary:     py2k: accept unicode literals on :func:`backref`, too

Fixed bug where in Py2K a unicode literal would not be accepted as the
string name of a class or other argument within declarative using
:func:`.backref` on :func:`.relationship`.

amends commit e6f67f48054d906856f879bc1803ea639aa4b670

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d5fd26b836af/
Changeset:   d5fd26b836af
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:46:45+00:00
Summary:     Merge remote-tracking branch 'origin/pr/212'

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/33c3aded3a19/
Changeset:   33c3aded3a19
Branch:      None
User:        Nils Philippsen
Date:        2015-11-30 17:49:12+00:00
Summary:     py2k: accept unicode literals on :func:`backref`, too

Fixed bug where in Py2K a unicode literal would not be accepted as the
string name of a class or other argument within declarative using
:func:`.backref` on :func:`.relationship`.

amends commit e6f67f48054d906856f879bc1803ea639aa4b670

(cherry picked from commit 58f73d2278393d813c7f39736fc96c5086f18f6d)

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ef85a0d18988/
Changeset:   ef85a0d18988
Branch:      None
User:        Nils Philippsen
Date:        2015-11-30 17:49:44+00:00
Summary:     py2k: accept unicode literals on :func:`backref`, too

Fixed bug where in Py2K a unicode literal would not be accepted as the
string name of a class or other argument within declarative using
:func:`.backref` on :func:`.relationship`.

amends commit e6f67f48054d906856f879bc1803ea639aa4b670

backport to rel_1_0

(cherry picked from commit 58f73d2278393d813c7f39736fc96c5086f18f6d)
(cherry picked from commit 33c3aded3a1944d93e9e6bca53e2f749980b8b09)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/be24b3ea8371/
Changeset:   be24b3ea8371
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:52:01+00:00
Summary:     - restore 'declarative' classifier

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/fcdfea202f19/
Changeset:   fcdfea202f19
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 17:52:17+00:00
Summary:     - restore 'declarative' classifier

(cherry picked from commit be24b3ea8371583d9ccd6fb834ae6f22f39c556e)

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

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

5 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6ab120558078/
Changeset:   6ab120558078
Branch:      None
User:        pgjones
Date:        2015-10-30 20:20:58+00:00
Summary:     Change generator termination from StopIteration to return.

>From [PEP 479](https://www.python.org/dev/peps/pep-0479/) the correct way to
terminate a generator is to return (which implicitly raises StopIteration)
rather than raise StopIteration.

Without this change using sqlalchemy in python 3.5 or greater results in
these warnings
    PendingDeprecationWarning: generator '__iter__' raised StopIteration
which this commit should remove.

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/a058233f55b2/
Changeset:   a058233f55b2
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:35:10+00:00
Summary:     Merge remote-tracking branch 'origin/pr/211'

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/735fb9295433/
Changeset:   735fb9295433
Branch:      None
User:        pgjones
Date:        2015-11-30 17:35:35+00:00
Summary:     Change generator termination from StopIteration to return.

>From [PEP 479](https://www.python.org/dev/peps/pep-0479/) the correct way to
terminate a generator is to return (which implicitly raises StopIteration)
rather than raise StopIteration.

Without this change using sqlalchemy in python 3.5 or greater results in
these warnings
    PendingDeprecationWarning: generator '__iter__' raised StopIteration
which this commit should remove.

(cherry picked from commit 6ab120558078bdcbfbe06d2ca55bd7a0d417bbb4)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4bb6770ae872/
Changeset:   4bb6770ae872
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 17:40:51+00:00
Summary:     - update changelog for all the py3.5/3.6 related prs at once

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/2c5ba60269c8/
Changeset:   2c5ba60269c8
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:41:10+00:00
Summary:     - update changelog for all the py3.5/3.6 related prs at once

(cherry picked from commit 4bb6770ae872b69bd65ba0d67a7e1453d1a4e14b)

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/03a3b5ffd302/
Changeset:   03a3b5ffd302
Branch:      None
User:        zzzeek
Date:        2015-11-30 17:19:26+00:00
Summary:     - A descriptive ValueError is now raised in the event that SQL server
returns an invalid date or time format from a DATE or TIME
column, rather than failing with a NoneType error.  Pull request
courtesy Ed Avis.
pullreq github:206

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/730aa2140c96/
Changeset:   730aa2140c96
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 17:20:23+00:00
Summary:     - A descriptive ValueError is now raised in the event that SQL server
returns an invalid date or time format from a DATE or TIME
column, rather than failing with a NoneType error.  Pull request
courtesy Ed Avis.
pullreq github:206

(cherry picked from commit 03a3b5ffd3027c79ce9b17b9388fd074e69b889d)

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

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

5 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d9178320d675/
Changeset:   d9178320d675
Branch:      None
User:        iurisilvio
Date:        2015-11-30 16:50:25+00:00
Summary:     Fix _assert_unorderable_types on py36.

The error message changed to:

`'<' not supported between instances of 'foo' and 'bar'`

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/2b39f09e73f6/
Changeset:   2b39f09e73f6
Branch:      None
User:        zzzeek
Date:        2015-11-30 16:53:09+00:00
Summary:     Merge remote-tracking branch 'origin/pr/218'

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ab87b518e146/
Changeset:   ab87b518e146
Branch:      None
User:        iurisilvio
Date:        2015-11-30 16:53:34+00:00
Summary:     Fix _assert_unorderable_types on py36.

The error message changed to:

`'<' not supported between instances of 'foo' and 'bar'`

(cherry picked from commit d9178320d6755d893638646503ed538b11b6536a)

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6657a008d664/
Changeset:   6657a008d664
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 16:55:03+00:00
Summary:     - update changelog to accommodate pr github:218

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/8145100da433/
Changeset:   8145100da433
Branch:      None
User:        zzzeek
Date:        2015-11-30 16:55:31+00:00
Summary:     - update changelog to accommodate pr github:218

(cherry picked from commit 6657a008d664c275c41a4beda967ddbb50b6ddec)

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

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

7 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e8a5ed9c1cbc/
Changeset:   e8a5ed9c1cbc
Branch:      None
User:        jaccarmac
Date:        2015-10-29 18:09:15+00:00
Summary:     Update usages of getargspec to compat version.

The places inspect.getargspec was being used were causing problems for
newer Python versions.

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/86e5419968be/
Changeset:   86e5419968be
Branch:      None
User:        zzzeek
Date:        2015-11-30 16:25:07+00:00
Summary:     - make inserted_primary_key a link and be more clear what happens here

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/62b1e37668ab/
Changeset:   62b1e37668ab
Branch:      None
User:        zzzeek
Date:        2015-11-30 16:25:51+00:00
Summary:     - make inserted_primary_key a link and be more clear what happens here

(cherry picked from commit 86e5419968be23b88ef7e2ba4de9ca6698f0540b)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/e45e4aa97d96/
Changeset:   e45e4aa97d96
Branch:      None
User:        zzzeek
Date:        2015-11-30 16:40:44+00:00
Summary:     Merge remote-tracking branch 'origin/pr/210'

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/67cebd902dad/
Changeset:   67cebd902dad
Branch:      None
User:        jaccarmac
Date:        2015-11-30 16:41:09+00:00
Summary:     Update usages of getargspec to compat version.

The places inspect.getargspec was being used were causing problems for
newer Python versions.

(cherry picked from commit e8a5ed9c1cbc5e9f0aebffad5ea78abb16167778)

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/3a4b89c5a00e/
Changeset:   3a4b89c5a00e
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 16:42:31+00:00
Summary:     - changelog for pr github:210

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/d59e951f4655/
Changeset:   d59e951f4655
Branch:      None
User:        zzzeek
Date:        2015-11-30 16:42:55+00:00
Summary:     - changelog for pr github:210

(cherry picked from commit 3a4b89c5a00ea7ea64ca42543041fc46a6907903)

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/4fcd93afb877/
Changeset:   4fcd93afb877
Branch:      None
User:        zzzeek
Date:        2015-11-30 02:50:50+00:00
Summary:     - close the session

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/d4fa1345ffe9/
Changeset:   d4fa1345ffe9
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-30 02:51:02+00:00
Summary:     - close the session

(cherry picked from commit 4fcd93afb877ec8929586c2d7b671aef1783d883)

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

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

13 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/fc73036865a0/
Changeset:   fc73036865a0
Branch:      None
User:        Gorka Eguileor
Date:        2015-09-24 13:35:13+00:00
Summary:     Preserve order in update method

In some DBs the UPDATE operation is order dependent, so the operation
behaves differently depending on the order of the values.

As an example, imagine a volumes table with columns 'status' and
'previous_status' and we want to update a volume that has 'available' in
the status column.

If the SQL query is performed as:

 UPDATE volumes SET previous_status=status, status='new' WHERE id=1;

This will result in a volume with 'new' status and 'available'
previous_status both on SQLite and MariaDB, but if we reverse the
columns:

 UPDATE volumes SET status='new', previous_status=status WHERE id=1;

We will get the same result in SQLite but will result in a volume with
status and previous_status set to 'new' in MariaDB, which is not what we
want.

So order must be taken into consideration in some cases and it should be
allowed to ve specified via the Query update method or the values method
of an update.

This patch fixes this issue by preserving the order of parameters in
updates and allowing to receive not only dictionaries in update and
values but also ordered dictionaries and list/tuples of value pairs
(like dict and OrderedDict do).

fixes #3541

Affected #:  10 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9fb76d759678/
Changeset:   9fb76d759678
Branch:      None
User:        Gorka Eguileor
Date:        2015-09-29 18:29:33+00:00
Summary:     Only preserve order in updates if tuple/dict

To avoid penalties for updates that do not require ordering, we will
only use OrderedDict for updates that receive a tuple or list of pairs,
and all kinds of dictionaries (dict, sqlalchemy's OrderedDict, or
collections.OrderedDict) will be treateated as unordered updates, just
like we were doing before.

This way this new feature will not change how updates behave for any
existing code and will only affect those that use the new ordered
feature.

This patch reverts update tests to how they were before as well as adds
a couple of tests to confirm that OrderedDicts are really treated like
normal dicts.

Affected #:  11 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ddb43cebf68b/
Changeset:   ddb43cebf68b
Branch:      None
User:        Gorka Eguileor
Date:        2015-09-30 16:45:05+00:00
Summary:     Postpone parameters change in ordered updates

Postpone as much as possible the change of update parameters to
OrderedDict from list or tuple of pairs.

This way we won't have problems with query's update method.

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ef816f23290a/
Changeset:   ef816f23290a
Branch:      None
User:        Gorka Eguileor
Date:        2015-10-02 16:22:33+00:00
Summary:     Only check once if parameters are ordered

Instead of checking multiple times if parameters are a dictionary in the
form of a tuple or list of value pairs, we check it only once and then
store it in the statement so it can be used on compilation time.

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c6ba1a7d4c2b/
Changeset:   c6ba1a7d4c2b
Branch:      None
User:        Gorka Eguileor
Date:        2015-10-05 08:42:09+00:00
Summary:     Remove dict comprehension for py26 compatibility

Remove added dict comprehensions that make this patch set non python 2.6
compatible.

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/44e5a31ccee5/
Changeset:   44e5a31ccee5
Branch:      None
User:        Gorka Eguileor
Date:        2015-10-08 11:24:02+00:00
Summary:     Reduce the numbers of calls to isinstance

Change _process_colparams method to remove duplicate isinstance calls
and try to speed up processing of the parameters.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1106bd3ff270/
Changeset:   1106bd3ff270
Branch:      None
User:        zzzeek
Date:        2015-11-25 23:19:36+00:00
Summary:     Merge remote-tracking branch 'origin/pr/200' into pr200

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ab0874e893af/
Changeset:   ab0874e893af
Branch:      None
User:        zzzeek
Date:        2015-11-26 00:39:17+00:00
Summary:     - work from an "explicit is better than implicit" perspective
here and require a flag on update() to use parameter ordering
rather than table ordering.   more docs/changelog notes are needed

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b8a825978e79/
Changeset:   b8a825978e79
Branch:      None
User:        zzzeek
Date:        2015-11-28 17:23:21+00:00
Summary:     - add tests for ordered params with onupdates

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/e9dfcd83ef43/
Changeset:   e9dfcd83ef43
Branch:      None
User:        zzzeek
Date:        2015-11-28 18:32:30+00:00
Summary:     - docs plus changelog for parameter ordered updates

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/3635408cd62a/
Changeset:   3635408cd62a
Branch:      pr200_updated
User:        zzzeek
Date:        2015-11-28 19:21:35+00:00
Summary:     - unfortunately, these are not the query.update() tests, these are
just session bind tests.  move / rework the preserve_parameter_order
tests to the appropriate module

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b0308a7b3af9/
Changeset:   b0308a7b3af9
Branch:      None
User:        zzzeek
Date:        2015-11-29 16:42:55+00:00
Summary:     - Fixed an issue in baked queries where the .get() method, used either
directly or within lazy loads, didn't consider the mapper's "get clause"
as part of the cache key, causing bound parameter mismatches if the
clause got re-generated.  This clause is cached by mappers
on the fly but in highly concurrent scenarios may be generated more
than once when first accessed.
fixes #3597

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/670fd506fe4c/
Changeset:   670fd506fe4c
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-29 16:43:30+00:00
Summary:     - Fixed an issue in baked queries where the .get() method, used either
directly or within lazy loads, didn't consider the mapper's "get clause"
as part of the cache key, causing bound parameter mismatches if the
clause got re-generated.  This clause is cached by mappers
on the fly but in highly concurrent scenarios may be generated more
than once when first accessed.
fixes #3597

(cherry picked from commit b0308a7b3af91cc61fbe3347376024ad8b7be019)

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/c90f0a49f332/
Changeset:   c90f0a49f332
Branch:      None
User:        zzzeek
Date:        2015-11-28 19:30:05+00:00
Summary:     - Added support for parameter-ordered SET clauses in an UPDATE
statement.  This feature is available by passing the
:paramref:`~.sqlalchemy.sql.expression.update.preserve_parameter_order`
flag either to the core :class:`.Update` construct or alternatively
adding it to the :paramref:`.Query.update.update_args` dictionary at
the ORM-level, also passing the parameters themselves as a list of 2-tuples.
Thanks to Gorka Eguileor for implementation and tests.
adapted from pullreq github:200

Affected #:  11 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d2d60acdcbd4/
Changeset:   d2d60acdcbd4
Branch:      rel_1_0
User:        zzzeek
Date:        2015-11-28 19:30:58+00:00
Summary:     - Added support for parameter-ordered SET clauses in an UPDATE
statement.  This feature is available by passing the
:paramref:`~.sqlalchemy.sql.expression.update.preserve_parameter_order`
flag either to the core :class:`.Update` construct or alternatively
adding it to the :paramref:`.Query.update.update_args` dictionary at
the ORM-level, also passing the parameters themselves as a list of 2-tuples.
Thanks to Gorka Eguileor for implementation and tests.
adapted from pullreq github:200

(cherry picked from commit c90f0a49f332867f6b337c79ddf192299788667f)

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