sqlalchemy-commits

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ae3f2abe06af/
Changeset:   ae3f2abe06af
Branch:      None
User:        zzzeek
Date:        2014-01-26 07:04:41
Summary:     updates

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/4a7acd40ce39/
Changeset:   4a7acd40ce39
Branch:      rel_0_8
User:        zzzeek
Date:        2014-01-26 07:04:46
Summary:     updates

Affected #:  1 file

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

--

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

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/da4256d3dc2f/
Changeset:   da4256d3dc2f
Branch:      rel_0_8
User:        zzzeek
Date:        2014-01-27 02:01:57
Summary:     docs

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d20d7549fd32/
Changeset:   d20d7549fd32
Branch:      None
User:        zzzeek
Date:        2014-01-27 02:02:08
Summary:     - docs

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/66fe0880bae3/
Changeset:   66fe0880bae3
Branch:      rel_0_8
User:        zzzeek
Date:        2014-01-29 23:09:50
Summary:     - add a test for [ticket:2927], which is an 0.9 issue but only because 0.8
isn't annotating correctly

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/8afb69ced876/
Changeset:   8afb69ced876
Branch:      None
User:        zzzeek
Date:        2014-01-29 23:33:28
Summary:     - Fixed regression whereby the "annotation" system used by the ORM was leaking
into the names used by standard functions in :mod:`sqlalchemy.sql.functions`,
such as ``func.coalesce()`` and ``func.max()``.  Using these functions
in ORM attributes and thus producing annotated versions of them could
corrupt the actual function name rendered in the SQL. [ticket:2927]

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/b8178a0bba35/
Changeset:   b8178a0bba35
Branch:      None
User:        zzzeek
Date:        2014-02-01 05:13:13
Summary:     - don't duplicate docs for Pool within QueuePool
- add huge warning regarding how use_threadlocal probably not what you want

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/5f144b2e4354/
Changeset:   5f144b2e4354
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-01 05:16:34
Summary:     - don't duplicate docs for Pool within QueuePool
- add huge warning regarding how use_threadlocal probably not what you want

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/9a3219bdac9a/
Changeset:   9a3219bdac9a
Branch:      ticket_2923
User:        zzzeek
Date:        2014-02-02 00:20:16
Summary:     - changelog
- docs
- support callables so that any token can be worked up

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/5b0919f3f5c7/
Changeset:   5b0919f3f5c7
Branch:      None
User:        zzzeek
Date:        2014-02-02 00:21:04
Summary:     - Added a new feature which allows automated naming conventions to be
applied to :class:`.Constraint` and :class:`.Index` objects.  Based
on a recipe in the wiki, the new feature uses schema-events to set up
names as various schema objects are associated with each other.  The
events then expose a configuration system through a new argument
:paramref:`.MetaData.naming_convention`.  This system allows production
of both simple and custom naming schemes for constraints and indexes
on a per-:class:`.MetaData` basis.  [ticket:2923]

commit 7e65e52c086652de3dd3303c723f98f09af54db8
Author: Mike Bayer <mi...@zz...>
Date:   Sat Feb 1 15:09:04 2014 -0500

    - first pass at new naming approach

Affected #:  8 files

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

--

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

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2d4b457924fa/
Changeset:   2d4b457924fa
Branch:      None
User:        zzzeek
Date:        2014-02-02 20:37:43
Summary:     - The behavior of :meth:`.Table.tometadata` has been adjusted such that
the schema target of a :class:`.ForeignKey` will not be changed unless
that schema matches that of the parent table.  That is, if
a table "schema_a.user" has a foreign key to "schema_b.order.id",
the "schema_b" target will be maintained whether or not the
"schema" argument is passed to :meth:`.Table.tometadata`.  However
if a table "schema_a.user" refers to "schema_a.order.id", the presence
of "schema_a" will be updated on both the parent and referred tables.
This is a behavioral change hence isn't likely to be backported to
0.8; it is assumed that the previous behavior is pretty buggy
however and that it's unlikely anyone was relying upon it.

Additionally, a new parameter has been added
:paramref:`.Table.tometadata.referred_schema_fn`.  This refers to a
callable function which will be used to determine the new referred
schema for any :class:`.ForeignKeyConstraint` encountered in the
tometadata operation.  This callable can be used to revert to the
previous behavior or to customize how referred schemas are treated
on a per-constraint basis.  [ticket:2913]

- rework the tests in test.sql.test_metadata, all the "tometadata" tests
now under new class ToMetaDataTest

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4ed4266803cb/
Changeset:   4ed4266803cb
Branch:      None
User:        zzzeek
Date:        2014-02-02 20:40:23
Summary:     - use from_statement() for the ORM column test
- with select_from(), add external order by so that Oracle orders correctly

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/064df1d1ee64/
Changeset:   064df1d1ee64
Branch:      None
User:        zzzeek
Date:        2014-02-03 01:19:24
Summary:     0.9.2

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/37d1f8983ce4/
Changeset:   37d1f8983ce4
Branch:      None
User:        zzzeek
Date:        2014-02-03 01:28:41
Summary:     typo

Affected #:  1 file

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

--

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

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d006198e17fc/
Changeset:   d006198e17fc
Branch:      None
User:        farvour
Date:        2014-02-05 22:40:55
Summary:     Add naming convention support when using schema in the metadata.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/c5dccd82dabf/
Changeset:   c5dccd82dabf
Branch:      None
User:        zzzeek
Date:        2014-02-05 22:54:31
Summary:     - Fixed regression in new "naming convention" feature where conventions
would fail if the referred table in a foreign key contained a schema
name.  Pull request courtesy Thomas Farvour. pullreq github:67

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/2a25e42c08e7/
Changeset:   2a25e42c08e7
Branch:      None
User:        zzzeek
Date:        2014-02-10 22:33:48
Summary:     - Fixed bug where :meth:`.Query.get` would fail to consistently
raise the :class:`.InvalidRequestError` that invokes when called
on a query with existing criterion, when the given identity is
already present in the identity map. [ticket:2951]

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/99717570ff08/
Changeset:   99717570ff08
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-10 22:34:19
Summary:     - Fixed bug where :meth:`.Query.get` would fail to consistently
raise the :class:`.InvalidRequestError` that invokes when called
on a query with existing criterion, when the given identity is
already present in the identity map. [ticket:2951]

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/093ce65c5fc7/
Changeset:   093ce65c5fc7
Branch:      None
User:        zzzeek
Date:        2014-02-10 22:37:32
Summary:     - dont need these extra conditions from the previous test

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/0470c5c5a68b/
Changeset:   0470c5c5a68b
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-10 22:37:59
Summary:     - dont need these extra conditions from the previous test

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/7d56f6c8077a/
Changeset:   7d56f6c8077a
Branch:      None
User:        zzzeek
Date:        2014-02-10 23:43:37
Summary:     this example doesn't work, we don't really have a solution for this as far as automating this pattern

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/50d60cfb9945/
Changeset:   50d60cfb9945
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-10 23:44:09
Summary:     this example doesn't work, we don't really have a solution for this as far as automating this pattern

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/036cb93abfb4/
Changeset:   036cb93abfb4
Branch:      None
User:        zzzeek
Date:        2014-02-13 21:19:12
Summary:     - Fixed bug where :meth:`.in_()` would go into an endless loop if
erroneously passed a column expression whose comparator included
the ``__getitem__()`` method, such as a column that uses the
:class:`.postgresql.ARRAY` type. [ticket:2957]

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b87935ed4409/
Changeset:   b87935ed4409
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-13 21:21:28
Summary:     - Fixed bug where :meth:`.in_()` would go into an endless loop if
erroneously passed a column expression whose comparator included
the ``__getitem__()`` method, such as a column that uses the
:class:`.postgresql.ARRAY` type. [ticket:2957]

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/ffa6f45ec392/
Changeset:   ffa6f45ec392
Branch:      None
User:        zzzeek
Date:        2014-02-14 20:32:00
Summary:     - Revised this very old issue where the Postgresql "get primary key"
reflection query were updated to take into account primary key constraints
that were renamed; the newer query fails on very old versions of
Postgresql such as version 7, so the old query is restored in those cases
when server_version_info < (8, 0) is detected. #2291

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/30febd7c193b/
Changeset:   30febd7c193b
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-14 20:32:30
Summary:     - Revised this very old issue where the Postgresql "get primary key"
reflection query were updated to take into account primary key constraints
that were renamed; the newer query fails on very old versions of
Postgresql such as version 7, so the old query is restored in those cases
when server_version_info < (8, 0) is detected. #2291

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/5330c02b7297/
Changeset:   5330c02b7297
Branch:      None
User:        zzzeek
Date:        2014-02-14 20:36:06
Summary:      this is for 0.9.3 also

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/28229a35e023/
Changeset:   28229a35e023
Branch:      None
User:        zzzeek
Date:        2014-02-14 20:39:41
Summary:     - Added server version detection to the newly added dialect startup
query for  "show standard_conforming_strings"; as this variable was
added as of PG 8.2, we skip the query for PG versions older than
that as well as for backends like Redshift. #2946

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/70ed9c8b559b/
Changeset:   70ed9c8b559b
Branch:      None
User:        zzzeek
Date:        2014-02-16 02:51:38
Summary:     - expand docs on MySQL table arguments beyond just storage engines
- clarify section on "foreign key reflection" and group this in a
section that refers to foreign keys.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/1a7b5d55c9a3/
Changeset:   1a7b5d55c9a3
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-16 02:52:33
Summary:     - expand docs on MySQL table arguments beyond just storage engines
- clarify section on "foreign key reflection" and group this in a
section that refers to foreign keys.

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/c3b1b554081d/
Changeset:   c3b1b554081d
Branch:      None
User:        zzzeek
Date:        2014-02-16 18:03:00
Summary:     - add documentation regarding native hstore flag, psycopg2
hstore extension. #2959

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/929ff9259848/
Changeset:   929ff9259848
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-16 18:03:53
Summary:     - add documentation regarding native hstore flag, psycopg2
hstore extension. #2959

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/dd32540dabbe/
Changeset:   dd32540dabbe
Branch:      None
User:        zzzeek
Date:        2014-02-19 16:48:32
Summary:     - Fixed a critical regression caused by :ticket:`2880` where the newly
concurrent ability to return connections from the pool means that the
"first_connect" event is now no longer synchronized either, thus leading
to dialect mis-configurations under even minimal concurrency situations.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4ac0558e1149/
Changeset:   4ac0558e1149
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-19 16:51:57
Summary:     - Fixed a critical regression caused by :ticket:`2880` where the newly
concurrent ability to return connections from the pool means that the
"first_connect" event is now no longer synchronized either, thus leading
to dialect mis-configurations under even minimal concurrency situations.

Conflicts:
	lib/sqlalchemy/event/attr.py

Affected #:  3 files

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

--

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

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/77ed03652580/
Changeset:   77ed03652580
Branch:      None
User:        zzzeek
Date:        2014-02-19 21:18:22
Summary:     - Fixed bug where calling :meth:`.Insert.values` with an empty list
or tuple would raise an IndexError.   It now produces an empty
insert construct as would be the case with an empty dictionary.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/506817a84e6b/
Changeset:   506817a84e6b
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-19 21:23:04
Summary:     - Fixed bug where calling :meth:`.Insert.values` with an empty list
or tuple would raise an IndexError.   It now produces an empty
insert construct as would be the case with an empty dictionary.

Conflicts:
	lib/sqlalchemy/sql/dml.py

Affected #:  3 files

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

--

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

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a552606091bf/
Changeset:   a552606091bf
Branch:      None
User:        zzzeek
Date:        2014-02-19 21:49:37
Summary:     - Added new MySQL-specific :class:`.mysql.DATETIME` which includes
fractional seconds support; also added fractional seconds support
to :class:`.mysql.TIMESTAMP`.  DBAPI support is limited, though
fractional seconds are known to be supported by MySQL Connector/Python.
Patch courtesy Geert JM Vanderkelen. #2941

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/dd6884eafaaf/
Changeset:   dd6884eafaaf
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-19 21:49:59
Summary:     - Added new MySQL-specific :class:`.mysql.DATETIME` which includes
fractional seconds support; also added fractional seconds support
to :class:`.mysql.TIMESTAMP`.  DBAPI support is limited, though
fractional seconds are known to be supported by MySQL Connector/Python.
Patch courtesy Geert JM Vanderkelen. #2941

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/8878e2307954/
Changeset:   8878e2307954
Branch:      None
User:        zzzeek
Date:        2014-02-19 22:11:19
Summary:     restore the check ahead of the lock to avoid using it after initialization
is done

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/f9059f6cd8cc/
Changeset:   f9059f6cd8cc
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-19 22:12:36
Summary:     restore check ahead of the lock to avoid locking when not needed

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/a0fb9e74c61b/
Changeset:   a0fb9e74c61b
Branch:      None
User:        zzzeek
Date:        2014-02-19 23:00:37
Summary:     - add a topological rule here to place PARTITIONS after PARTITION_BY,
for output consistency within the tests as well as in practice

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/bfdb51ac6a4b/
Changeset:   bfdb51ac6a4b
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-19 23:01:26
Summary:     - add a topological rule here to place PARTITIONS after PARTITION_BY,
for output consistency within the tests as well as in practice

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/25831872db7f/
Changeset:   25831872db7f
Branch:      None
User:        zzzeek
Date:        2014-02-20 01:04:04
Summary:     - Fixed bug in SQLite "join rewriting" where usage of an exists() construct
would fail to be rewritten properly, such as when the exists is
mapped to a column_property in an intricate nested-join scenario. #2967

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/69d1d08dc398/
Changeset:   69d1d08dc398
Branch:      None
User:        zzzeek
Date:        2014-02-20 01:12:40
Summary:     - re: #2967, also fixed a somewhat related issue where join rewriting would fail
on the columns clause of the SELECT statement if the targets were
aliased tables, as opposed to individual aliased columns.

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/57b214a0a446/
Changeset:   57b214a0a446
Branch:      None
User:        zzzeek
Date:        2014-02-20 01:22:17
Summary:     - Added an additional message to psycopg2 disconnect detection,
"could not send data to server", which complements the existing
"could not receive data from server" and has been observed by users,
fixes #2936

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/cd0d29cef4c6/
Changeset:   cd0d29cef4c6
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-20 01:22:48
Summary:     - Added an additional message to psycopg2 disconnect detection,
"could not send data to server", which complements the existing
"could not receive data from server" and has been observed by users,
fixes #2936

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/e21cd0d95fb6/
Changeset:   e21cd0d95fb6
Branch:      None
User:        zzzeek
Date:        2014-02-28 01:54:49
Summary:     - Fixed bug in :func:`.tuple_` construct where the "type" of essentially
the first SQL expression would be applied as the "comparison type"
to a compared tuple value; this has the effect in some cases of an
inappropriate "type coersion" occurring, such as when a tuple that
has a mix of String and Binary values improperly coerces target
values to Binary even though that's not what they are on the left
side.  :func:`.tuple_` now expects heterogeneous types within its
list of values.
fixes #2977

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/3ba1385520a0/
Changeset:   3ba1385520a0
Branch:      rel_0_8
User:        zzzeek
Date:        2014-02-28 01:57:20
Summary:     - Fixed bug in :func:`.tuple_` construct where the "type" of essentially
the first SQL expression would be applied as the "comparison type"
to a compared tuple value; this has the effect in some cases of an
inappropriate "type coersion" occurring, such as when a tuple that
has a mix of String and Binary values improperly coerces target
values to Binary even though that's not what they are on the left
side.  :func:`.tuple_` now expects heterogeneous types within its
list of values.
fixes #2977

Conflicts:
	lib/sqlalchemy/sql/elements.py
	test/sql/test_operators.py

Affected #:  3 files

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

--

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

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a203233a1196/
Changeset:   a203233a1196
Branch:      None
User:        zzzeek
Date:        2014-03-03 19:27:32
Summary:     - transfer to non-unittest usage.  a little more tricky.

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/23d9778514fe/
Changeset:   23d9778514fe
Branch:      multi_db_tests
User:        zzzeek
Date:        2014-03-03 19:41:38
Summary:     figure out module location a bit better

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.