sqlalchemy-commits

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/65010e97bca9/
Changeset:   65010e97bca9
Branch:      None
User:        zzzeek
Date:        2016-01-23 19:58:42+00:00
Summary:     - use uuid fragments for provision names to enable multiple test suites
per server

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/bea513385566/
Changeset:   bea513385566
Branch:      rel_1_0
User:        zzzeek
Date:        2016-01-23 19:59:03+00:00
Summary:     - use uuid fragments for provision names to enable multiple test suites
per server

(cherry picked from commit 65010e97bca995657c2843f6aa8ad48bab370182)

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/2419bfe34cd5/
Changeset:   2419bfe34cd5
Branch:      None
User:        zzzeek
Date:        2016-01-23 22:31:02+00:00
Summary:     - fix stray connection

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/baacacaad879/
Changeset:   baacacaad879
Branch:      rel_1_0
User:        zzzeek
Date:        2016-01-23 22:31:13+00:00
Summary:     - fix stray connection

(cherry picked from commit 2419bfe34cd5a1f4ead67d556ba74f3f1950762b)

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/7d70dfd412c0/
Changeset:   7d70dfd412c0
Branch:      rel_1_0
User:        zzzeek
Date:        2016-01-23 23:30:37+00:00
Summary:     - fix array test that was essentially taking a weird guess
at the primary key of a row based on other tests invoking around it

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/926784f51361/
Changeset:   926784f51361
Branch:      None
User:        zzzeek
Date:        2016-01-23 23:31:07+00:00
Summary:     - fix array test that was essentially taking a weird guess
at the primary key of a row based on other tests invoking around it

(cherry picked from commit 7d70dfd412c05fd8349339da01b472bd3df02082)

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/5742e321b261/
Changeset:   5742e321b261
Branch:      None
User:        zzzeek
Date:        2016-01-26 22:28:40+00:00
Summary:     - unfortunately we need to match within join where col.key does not match
what's given so we need to use a set() here.  contains_column is not within
any performance paths

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/b11bfd5b0c72/
Changeset:   b11bfd5b0c72
Branch:      rel_1_0
User:        zzzeek
Date:        2016-01-26 22:29:09+00:00
Summary:     - unfortunately we need to match within join where col.key does not match
what's given so we need to use a set() here.  contains_column is not within
any performance paths

(cherry picked from commit 5742e321b261c0c1303835b80418cd3cdc1b5643)

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/8a1e619fb20d/
Changeset:   8a1e619fb20d
Branch:      None
User:        zzzeek
Date:        2016-01-28 20:01:31+00:00
Summary:     - revert the change first made in a6fe4dc, as we are now generalizing
the warning here to all safe_reraise() cases in Python 2.
- Revisiting :ticket:`2696`, first released in 1.0.10, which attempts to
work around Python 2's lack of exception context reporting by emitting
a warning for an exception that was interrupted by a second exception
when attempting to roll back the already-failed transaction; this
issue continues to occur for MySQL backends in conjunction with a
savepoint that gets unexpectedly lost, which then causes a
"no such savepoint" error when the rollback is attempted, obscuring
what the original condition was.

The approach has been generalized to the Core "safe
reraise" function which takes place across the ORM and Core in any
place that a transaction is being rolled back in response to an error
which occurred trying to commit, including the context managers
provided by :class:`.Session` and :class:`.Connection`, and taking
place for operations such as a failure on "RELEASE SAVEPOINT".
Previously, the fix was only in place for a specific path within
the ORM flush/commit process; it now takes place for all transational
context managers as well.
fixes #2696

Affected #:  7 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7a7483c0cf2f/
Changeset:   7a7483c0cf2f
Branch:      rel_1_0
User:        zzzeek
Date:        2016-01-28 20:02:49+00:00
Summary:     - revert the change first made in a6fe4dc, as we are now generalizing
the warning here to all safe_reraise() cases in Python 2.
- Revisiting :ticket:`2696`, first released in 1.0.10, which attempts to
work around Python 2's lack of exception context reporting by emitting
a warning for an exception that was interrupted by a second exception
when attempting to roll back the already-failed transaction; this
issue continues to occur for MySQL backends in conjunction with a
savepoint that gets unexpectedly lost, which then causes a
"no such savepoint" error when the rollback is attempted, obscuring
what the original condition was.

The approach has been generalized to the Core "safe
reraise" function which takes place across the ORM and Core in any
place that a transaction is being rolled back in response to an error
which occurred trying to commit, including the context managers
provided by :class:`.Session` and :class:`.Connection`, and taking
place for operations such as a failure on "RELEASE SAVEPOINT".
Previously, the fix was only in place for a specific path within
the ORM flush/commit process; it now takes place for all transational
context managers as well.
fixes #2696

(cherry picked from commit 8a1e619fb20df1be6ad2e0c563e451e17eb17628)

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/859379e2fcc4/
Changeset:   859379e2fcc4
Branch:      None
User:        zzzeek
Date:        2016-01-29 16:20:22+00:00
Summary:     - happy new year

Affected #:  177 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/631afa456fa9/
Changeset:   631afa456fa9
Branch:      rel_1_0
User:        zzzeek
Date:        2016-01-29 16:25:37+00:00
Summary:     - happy new year

(cherry picked from commit 859379e2fcc4506d036700ba1eca4c0ae526a8ee)

Affected #:  172 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/c8b3d4ed3f26/
Changeset:   c8b3d4ed3f26
Branch:      None
User:        zzzeek
Date:        2016-01-29 17:19:17+00:00
Summary:     - put a retry in for PG database provisioning as it locks
on database use

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/786c21b9a41c/
Changeset:   786c21b9a41c
Branch:      rel_1_0
User:        zzzeek
Date:        2016-01-29 17:20:43+00:00
Summary:     - put a retry in for PG database provisioning as it locks
on database use

(cherry picked from commit c8b3d4ed3f2638599fc73486cf0f724fa033a638)

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/e0a580b3d055/
Changeset:   e0a580b3d055
Branch:      None
User:        zzzeek
Date:        2016-02-02 15:20:54+00:00
Summary:     - Fixed issue where inadvertent use of the Python ``__contains__``
override with a column expression (e.g. by using ``'x' in col``)
would cause an endless loop in the case of an ARRAY type, as Python
defers this to ``__getitem__`` access which never raises for this
type.  Overall, all use of ``__contains__`` now raises
NotImplementedError.
fixes #3642

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/69f6a8d714c0/
Changeset:   69f6a8d714c0
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-02 15:41:01+00:00
Summary:     - Fixed issue where inadvertent use of the Python ``__contains__``
override with a column expression (e.g. by using ``'x' in col``)
would cause an endless loop in the case of an ARRAY type, as Python
defers this to ``__getitem__`` access which never raises for this
type.  Overall, all use of ``__contains__`` now raises
NotImplementedError.
fixes #3642

(cherry picked from commit e0a580b3d055a600afae61840058a5a30ef5fe74)

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/fd07c22e6e10/
Changeset:   fd07c22e6e10
Branch:      None
User:        zzzeek
Date:        2016-02-04 18:36:45+00:00
Summary:     - add an impl for Enum to Oracle which has subclassing requirements
on unicode.   Enum would be better as a TypeDecorator
at this point but then that becomes awkward with native enum
types (Interval works that way, but we don't need the bind_processor for
native interval...)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/c70d7226ee1c/
Changeset:   c70d7226ee1c
Branch:      None
User:        zzzeek
Date:        2016-02-04 18:59:32+00:00
Summary:     - add a session killer for oracle provisioning

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/0f6d1b7efbed/
Changeset:   0f6d1b7efbed
Branch:      None
User:        zzzeek
Date:        2016-02-08 21:27:44+00:00
Summary:     - py3k fix for enum feature

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/7cb2a2d6c0cb/
Changeset:   7cb2a2d6c0cb
Branch:      master
User:        zzzeek
Date:        2016-02-08 21:27:55+00:00
Summary:     - additional fixes to get oracle + multiprocess to be reliable

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/00a05e357b5b/
Changeset:   00a05e357b5b
Branch:      None
User:        zzzeek
Date:        2016-02-09 03:56:02+00:00
Summary:     - use config-based test schema

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/11a8440bc43a/
Changeset:   11a8440bc43a
Branch:      master
User:        zzzeek
Date:        2016-02-09 03:57:02+00:00
Summary:     - Testing reveals that we have *no* weak references to any cx_Oracle connections at all,
yet cx_Oracle still has open sessions that cannot be killed until process dies.
Oracle wins!   Add a completely separate DB reaper script that runs
after py.test is done.

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/29dcaa2b0ae2/
Changeset:   29dcaa2b0ae2
Branch:      None
User:        zzzeek
Date:        2016-02-09 23:05:40+00:00
Summary:     - Fixed bug in :func:`.expression.text` construct where a double-colon
expression would not escape properly, e.g. ``some\:\:expr``, as is most
commonly required when rendering Postgresql-style CAST expressions.
fixes #3644

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/498b0729b271/
Changeset:   498b0729b271
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-09 23:06:15+00:00
Summary:     - Fixed bug in :func:`.expression.text` construct where a double-colon
expression would not escape properly, e.g. ``some\:\:expr``, as is most
commonly required when rendering Postgresql-style CAST expressions.
fixes #3644

(cherry picked from commit 29dcaa2b0ae2d26b36ec624be80f56e03ab9095e)

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/3f1f1895ac99/
Changeset:   3f1f1895ac99
Branch:      None
User:        zzzeek
Date:        2016-02-10 02:08:21+00:00
Summary:     - don't drop the ts1/ts2 databases without seeing the primary DB,
because we never log in on the ts1/ts2.  races against other runs
and erases their DBs

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/d802bcb8dfba/
Changeset:   d802bcb8dfba
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-10 02:09:06+00:00
Summary:     - don't drop the ts1/ts2 databases without seeing the primary DB,
because we never log in on the ts1/ts2.  races against other runs
and erases their DBs

(cherry picked from commit 3f1f1895ac99963da1a989c69c2dce59ae916ffc)

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/287aaa9d416b/
Changeset:   287aaa9d416b
Branch:      None
User:        zzzeek
Date:        2016-02-10 15:17:45+00:00
Summary:     - add more documentation to MutableDict explaining
that this structure is only intended to track additions
and removals from the dictionary, not recursive tracking
of embedded changes.  fixes #3646.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/3215a2dac0e5/
Changeset:   3215a2dac0e5
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-10 15:18:01+00:00
Summary:     - add more documentation to MutableDict explaining
that this structure is only intended to track additions
and removals from the dictionary, not recursive tracking
of embedded changes.  fixes #3646.

(cherry picked from commit 287aaa9d416b4f72179da320af0624b9ebc43846)

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/366f97b5617a/
Changeset:   366f97b5617a
Branch:      None
User:        zzzeek
Date:        2016-02-12 03:29:18+00:00
Summary:     - Fixed bug in :meth:`.Session.merge` where an object with a composite
primary key that has values for some but not all of the PK fields
would emit a SELECT statement leaking the internal NEVER_SET symbol
into the query, rather than detecting that this object does not have
a searchable primary key and no SELECT should be emitted.
fixes #3647

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/a74b028f9f5b/
Changeset:   a74b028f9f5b
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-12 03:31:44+00:00
Summary:     - Fixed bug in :meth:`.Session.merge` where an object with a composite
primary key that has values for some but not all of the PK fields
would emit a SELECT statement leaking the internal NEVER_SET symbol
into the query, rather than detecting that this object does not have
a searchable primary key and no SELECT should be emitted.
fixes #3647

(cherry picked from commit 366f97b5617af0d15cfaf594ec5ef0408c70e873)

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/01809bddff5b/
Changeset:   01809bddff5b
Branch:      None
User:        zzzeek
Date:        2016-02-22 01:52:43+00:00
Summary:     - Fixed bug in "to_list" conversion where a single bytes object
would be turned into a list of individual characters.  This would
impact among other things using the :meth:`.Query.get` method
on a primary key that's a bytes object.
fixes #3660

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c87d0bff3ada/
Changeset:   c87d0bff3ada
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-22 01:53:21+00:00
Summary:     - Fixed bug in "to_list" conversion where a single bytes object
would be turned into a list of individual characters.  This would
impact among other things using the :meth:`.Query.get` method
on a primary key that's a bytes object.
fixes #3660

(cherry picked from commit 01809bddff5b6e93010eb139aed54526c6e6c058)

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/aa9ce3f521f2/
Changeset:   aa9ce3f521f2
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-22 03:46:31+00:00
Summary:     - additional adjustment to the fix made in 8ad968f33100baeb3b13c7e0b724b6b79ab4277f
for ref #3657.  The Oracle dialect makes more use of the "select_wraps_for"
feature than SQL server because Oracle doesn't have "TOP" for a limit-only
select, so tests are showing more happening here.  In the case where
the select() has some dupe columns, these are deduped from the .c collection
so a positional match between the wrapper and original can't use .inner_columns,
because these collections wont match.  Using _columns_plus_names
instead which is the deduped collection that determines the SELECT display,
which definitely have to match up.

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/eff7b4f29d2a/
Changeset:   eff7b4f29d2a
Branch:      None
User:        zzzeek
Date:        2016-02-22 03:49:29+00:00
Summary:     - additional adjustment to the fix made in 8ad968f33100baeb3b13c7e0b724b6b79ab4277f
for ref #3657.  The Oracle dialect makes more use of the "select_wraps_for"
feature than SQL server because Oracle doesn't have "TOP" for a limit-only
select, so tests are showing more happening here.  In the case where
the select() has some dupe columns, these are deduped from the .c collection
so a positional match between the wrapper and original can't use .inner_columns,
because these collections wont match.  Using _columns_plus_names
instead which is the deduped collection that determines the SELECT display,
which definitely have to match up.

(cherry picked from commit aa9ce3f521f254da9879ede011e520ec35b8270e)

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/0210695bd97e/
Changeset:   0210695bd97e
Branch:      None
User:        zzzeek
Date:        2016-02-26 05:20:39+00:00
Summary:     - Anonymous labeling is applied to a :attr:`.func` construct that is
passed to :func:`.column_property`, so that if the same attribute
is referred to as a column expression twice the names are de-duped,
thus avoiding "ambiguous column" errors.   Previously, the
``.label(None)`` would need to be applied in order for the name
to be de-anonymized.
fixes #3663

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/aac2cb5007ce/
Changeset:   aac2cb5007ce
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-26 05:21:12+00:00
Summary:     - Anonymous labeling is applied to a :attr:`.func` construct that is
passed to :func:`.column_property`, so that if the same attribute
is referred to as a column expression twice the names are de-duped,
thus avoiding "ambiguous column" errors.   Previously, the
``.label(None)`` would need to be applied in order for the name
to be de-anonymized.
fixes #3663

(cherry picked from commit 0210695bd97e76f58d8781b69337816501482fb0)

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/785224a92f39/
Changeset:   785224a92f39
Branch:      rel_1_0
User:        zzzeek
Date:        2016-02-26 16:27:12+00:00
Summary:     - unfortunately calling upon "_label" here makes it unclear if
we're trying to hit columns without names yet and such, to suit the bug
right now just make it specific to FunctionElement

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/8a20d277c52b/
Changeset:   8a20d277c52b
Branch:      None
User:        zzzeek
Date:        2016-02-26 16:27:49+00:00
Summary:     - unfortunately calling upon "_label" here makes it unclear if
we're trying to hit columns without names yet and such, to suit the bug
right now just make it specific to FunctionElement

(cherry picked from commit 785224a92f39bd5bdd05bbc66f4dd79736abded5)

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/0e7904e730c3/
Changeset:   0e7904e730c3
Branch:      None
User:        zzzeek
Date:        2016-03-03 15:50:18+00:00
Summary:     - not sure why MySQL DROP DBs fail but we can't just ignore the error
like this

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/8bc90c066b52/
Changeset:   8bc90c066b52
Branch:      rel_1_0
User:        zzzeek
Date:        2016-03-03 15:50:38+00:00
Summary:     - not sure why MySQL DROP DBs fail but we can't just ignore the error
like this

(cherry picked from commit 0e7904e730c3d2b0d3a394ad60010158ee29050c)

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/be7f8e0b8110/
Changeset:   be7f8e0b8110
Branch:      None
User:        zzzeek
Date:        2016-03-08 14:28:44+00:00
Summary:     - skip GC tests here when coverage is enabled, seems to interfere

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/a7491feb6c21/
Changeset:   a7491feb6c21
Branch:      rel_1_0
User:        zzzeek
Date:        2016-03-08 14:29:07+00:00
Summary:     - skip GC tests here when coverage is enabled, seems to interfere

(cherry picked from commit be7f8e0b81106c21fa7956f0c27cf207375681c4)

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/edbb32649960/
Changeset:   edbb32649960
Branch:      None
User:        zzzeek
Date:        2016-03-15 22:01:23+00:00
Summary:     - ensure engine is restored even if we had a failure in cleanup
for stray connection

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/9c2515c80fb2/
Changeset:   9c2515c80fb2
Branch:      rel_1_0
User:        zzzeek
Date:        2016-03-15 22:01:43+00:00
Summary:     - ensure engine is restored even if we had a failure in cleanup
for stray connection

(cherry picked from commit edbb32649960db29761e765fc74c025e9999c7dd)

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/732c613eeb89/
Changeset:   732c613eeb89
Branch:      None
User:        Benjamin Dopplinger
Date:        2016-03-16 03:30:04+00:00
Summary:     Fix typo
Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/e3ea0c8b961b/
Changeset:   e3ea0c8b961b
Branch:      rel_1_0
User:        Benjamin Dopplinger
Date:        2016-03-17 01:01:57+00:00
Summary:     Fix typo
(cherry picked from commit 732c613eeb890e7b7cbd04750468dac584151a31)

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/07a4b6cbcda6/
Changeset:   07a4b6cbcda6
Branch:      None
User:        zzzeek
Date:        2016-03-21 14:57:40+00:00
Summary:     - Fixed bug where the negation of an EXISTS expression would not
be properly typed as boolean in the result, and also would fail to be
anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
fixes #3682

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/dfe49c7b7f0c/
Changeset:   dfe49c7b7f0c
Branch:      rel_1_0
User:        zzzeek
Date:        2016-03-21 14:58:08+00:00
Summary:     - Fixed bug where the negation of an EXISTS expression would not
be properly typed as boolean in the result, and also would fail to be
anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
fixes #3682

(cherry picked from commit 07a4b6cbcda6e6ee6e67893c5a5d2fd01e5f125f)

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/4a3205df84b7/
Changeset:   4a3205df84b7
Branch:      None
User:        Patrick
Date:        2016-03-30 20:45:40+00:00
Summary:     Docstring Fix

Change the docstring in short_selects example to match the code

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/fb7e141abd7e/
Changeset:   fb7e141abd7e
Branch:      rel_1_0
User:        Patrick
Date:        2016-03-30 21:01:21+00:00
Summary:     Docstring Fix

Change the docstring in short_selects example to match the code

(cherry picked from commit 4a3205df84b737f5fe55914fe22eef7264f20764)

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.