sqlalchemy-commits

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/3f7b3185469d/
Changeset:   3f7b3185469d
Branch:      None
User:        zzzeek
Date:        2013-06-26 06:56:09
Summary:     - lots of docs
- however i might remove the "froms" argument...

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1b6b2fb8d2ea/
Changeset:   1b6b2fb8d2ea
Branch:      ticket_2746
User:        zzzeek
Date:        2013-06-26 07:59:50
Summary:     - based on the insight that a SELECT can correlate anything that ultimately
came from an enclosing SELECT that links to this one via WHERE/columns/HAVING/ORDER BY,
have the compiler keep track of the FROM lists that correspond in this way,
link it to the asfrom flag, so that we send to _get_display_froms() the exact
list of candidate FROMs to correlate.  no longer need any asfrom logic in the
Select() itself and the whole "froms" argument goes away, the test cases in

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/3e52710a7985/
Changeset:   3e52710a7985
Branch:      master
User:        zzzeek
Date:        2013-06-26 21:03:50
Summary:     add an ORDER BY here

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/d64c945eae68/
Changeset:   d64c945eae68
Branch:      rel_0_8
User:        zzzeek
Date:        2013-06-26 21:04:08
Summary:     add an ORDER BY here

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/04b66bc5e7b8/
Changeset:   04b66bc5e7b8
Branch:      master
User:        zzzeek
Date:        2013-06-28 17:35:57
Summary:     Fixed bug in HSTORE type where keys/values that contained
backslashed quotes would not be escaped correctly when
using the "non native" (i.e. non-psycopg2) means
of translating HSTORE data.  Patch courtesy Ryan Kelly.
[ticket:2766]

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/69179e009c2d/
Changeset:   69179e009c2d
Branch:      rel_0_8
User:        zzzeek
Date:        2013-06-28 17:38:28
Summary:     Fixed bug in HSTORE type where keys/values that contained
backslashed quotes would not be escaped correctly when
using the "non native" (i.e. non-psycopg2) means
of translating HSTORE data.  Patch courtesy Ryan Kelly.
[ticket:2766]

Conflicts:
	doc/build/changelog/changelog_09.rst
	lib/sqlalchemy/dialects/postgresql/hstore.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/bccf8ff5b1b1/
Changeset:   bccf8ff5b1b1
Branch:      master
User:        zzzeek
Date:        2013-06-28 17:49:41
Summary:     Type lookup when reflecting the Firebird types LONG and
INT64 has been fixed so that LONG is treated as INTEGER,
INT64 treated as BIGINT, unless the type has a "precision"
in which case it's treated as NUMERIC.  Patch courtesy
Russell Stuart.
[ticket:2757]

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/f57fc6836f47/
Changeset:   f57fc6836f47
Branch:      rel_0_8
User:        zzzeek
Date:        2013-06-28 17:50:27
Summary:     Type lookup when reflecting the Firebird types LONG and
INT64 has been fixed so that LONG is treated as INTEGER,
INT64 treated as BIGINT, unless the type has a "precision"
in which case it's treated as NUMERIC.  Patch courtesy
Russell Stuart.
[ticket:2757]

Conflicts:
	doc/build/changelog/changelog_09.rst

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/3b24ccaf28fd/
Changeset:   3b24ccaf28fd
Branch:      master
User:        zzzeek
Date:        2013-06-30 17:09:37
Summary:     A warning is emitted when trying to flush an object of an inherited
mapped class where the polymorphic discriminator has been assigned
to a value that is invalid for the class.   [ticket:2750]

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ead7d9a68091/
Changeset:   ead7d9a68091
Branch:      rel_0_8
User:        zzzeek
Date:        2013-06-30 17:11:35
Summary:     A warning is emitted when trying to flush an object of an inherited
mapped class where the polymorphic discriminator has been assigned
to a value that is invalid for the class.   [ticket:2750]

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/1d67b2a23364/
Changeset:   1d67b2a23364
Branch:      rel_0_8
User:        zzzeek
Date:        2013-06-30 17:21:19
Summary:     add better tests for [ticket:2750]

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/6ece30569239/
Changeset:   6ece30569239
Branch:      master
User:        zzzeek
Date:        2013-06-30 17:21:43
Summary:     add better tests for [ticket:2750]

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/715d6cf3d10a/
Changeset:   715d6cf3d10a
Branch:      master
User:        zzzeek
Date:        2013-06-30 21:58:50
Summary:     - additional fix for [ticket:2750] where on an update, we make sure the
value is present

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d4b850fa6bb7/
Changeset:   d4b850fa6bb7
Branch:      rel_0_8
User:        zzzeek
Date:        2013-06-30 21:59:26
Summary:     - additional fix for [ticket:2750] where on an update, we make sure the
value is present

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/1eaa003e023a/
Changeset:   1eaa003e023a
Branch:      master
User:        zzzeek
Date:        2013-07-01 02:15:21
Summary:     fix syntax screwup

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/63f157b18abd/
Changeset:   63f157b18abd
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-01 02:15:47
Summary:     fix syntax screwup

Conflicts:
	doc/build/changelog/changelog_09.rst

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/b8046baf7443/
Changeset:   b8046baf7443
Branch:      None
User:        zzzeek
Date:        2013-07-01 03:11:56
Summary:     fix a missing stringio import

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/1bdd0bac3f01/
Changeset:   1bdd0bac3f01
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-01 05:38:45
Summary:     fix python 2.5isms

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/0e219f2eff89/
Changeset:   0e219f2eff89
Branch:      master
User:        zzzeek
Date:        2013-07-03 00:02:20
Summary:     ORM descriptors such as hybrid properties can now be referenced
by name in a string argument used with ``order_by``,
``primaryjoin``, or similar in :func:`.relationship`,
in addition to column-bound attributes. [ticket:2761]

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/761414a07be3/
Changeset:   761414a07be3
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-03 00:02:56
Summary:     ORM descriptors such as hybrid properties can now be referenced
by name in a string argument used with ``order_by``,
``primaryjoin``, or similar in :func:`.relationship`,
in addition to column-bound attributes. [ticket:2761]

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/1fb6c4a33d67/
Changeset:   1fb6c4a33d67
Branch:      master
User:        zzzeek
Date:        2013-07-03 00:10:08
Summary:     Added :class:`.BIGINT` to the list of type names that can be
reflected by the SQLite dialect; courtesy Russell Stuart.
[ticket:2764]

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/2180cf44e585/
Changeset:   2180cf44e585
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-03 00:11:31
Summary:     Added :class:`.BIGINT` to the list of type names that can be
reflected by the SQLite dialect; courtesy Russell Stuart.
[ticket:2764]

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/b1e1bf8e674f/
Changeset:   b1e1bf8e674f
Branch:      master
User:        zzzeek
Date:        2013-07-03 00:24:58
Summary:     Fixed bug when using multi-table UPDATE where a supplemental
table is a SELECT with its own bound parameters, where the positioning
of the bound parameters would be reversed versus the statement
itself when using MySQL's special syntax.
[ticket:2768]

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9c5a13f0495c/
Changeset:   9c5a13f0495c
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-03 00:25:35
Summary:     Fixed bug when using multi-table UPDATE where a supplemental
table is a SELECT with its own bound parameters, where the positioning
of the bound parameters would be reversed versus the statement
itself when using MySQL's special syntax.
[ticket:2768]

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/a4e59730d541/
Changeset:   a4e59730d541
Branch:      None
User:        zzzeek
Date:        2013-07-03 01:06:30
Summary:     genericize tests here

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/fabd1992465e/
Changeset:   fabd1992465e
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-03 01:12:49
Summary:     - clean up some of the requires for cross-schema reflection
- add oracle profile counts

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/167adac5dc5e/
Changeset:   167adac5dc5e
Branch:      master
User:        zzzeek
Date:        2013-07-03 02:35:01
Summary:     for this test, apparently we don't handle sets as unordered since neither does
MySQL.  for some reason set ordering was constant when testing mysqldb, but not
so with oursql.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/e68377b95b57/
Changeset:   e68377b95b57
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-03 02:36:23
Summary:     for this test, apparently we don't handle sets as unordered since neither does
MySQL.  for some reason set ordering was constant when testing mysqldb, but not
so with oursql.

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/52293e3d4cb9/
Changeset:   52293e3d4cb9
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-03 19:47:44
Summary:     make this rule automatic based on coverage plugin

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/bc705e28cfd8/
Changeset:   bc705e28cfd8
Branch:      master
User:        zzzeek
Date:        2013-07-03 19:48:05
Summary:     make this rule automatic based on coverage plugin

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/f9ec82d22f63/
Changeset:   f9ec82d22f63
Branch:      master
User:        zzzeek
Date:        2013-07-03 21:38:26
Summary:     dont need this

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/55b664622d6e/
Changeset:   55b664622d6e
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-03 21:38:45
Summary:     dont need this

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/f390639bf1a7/
Changeset:   f390639bf1a7
Branch:      master
User:        zzzeek
Date:        2013-07-04 19:18:00
Summary:     Fixed bug where :class:`.QueuePool` would lose the correct
checked out count if an existing pooled connection failed to reconnect
after an invalidate or recycle event.  Also in 0.8.3.
[ticket:2772]

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4a9d88b1cf1b/
Changeset:   4a9d88b1cf1b
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-04 19:25:40
Summary:     - take advantage of 0.9's pool redesign a bit, adding
_ConnectionRecord.checkin() so that this functionality is
encapsulated; is now called from two different locations
for [ticket:2772].
- Fixed bug where :class:`.QueuePool` would lose the correct
checked out count if an existing pooled connection failed to reconnect
after an invalidate or recycle event. [ticket:2772]

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/cec89cae1569/
Changeset:   cec89cae1569
Branch:      master
User:        zzzeek
Date:        2013-07-05 21:51:24
Summary:     - Added new method to the :func:`.insert` construct
:meth:`.Insert.from_select`.  Given a list of columns and
a selectable, renders ``INSERT INTO (table) (columns) SELECT ..``.
While this feature is highlighted as part of 0.9 it is also
backported to 0.8.3. [ticket:722]
- The :func:`.update`, :func:`.insert`, and :func:`.delete` constructs
will now interpret ORM entities as FROM clauses to be operated upon,
in the same way that select() already does.  Also in 0.8.3.

Affected #:  10 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/8373d7599eda/
Changeset:   8373d7599eda
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-05 21:52:34
Summary:     - Added new method to the :func:`.insert` construct
:meth:`.Insert.from_select`.  Given a list of columns and
a selectable, renders ``INSERT INTO (table) (columns) SELECT ..``.
While this feature is highlighted as part of 0.9 it is also
backported to 0.8.3. [ticket:722]
- The :func:`.update`, :func:`.insert`, and :func:`.delete` constructs
will now interpret ORM entities as FROM clauses to be operated upon,
in the same way that select() already does.

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/71c47ac7ae78/
Changeset:   71c47ac7ae78
Branch:      master
User:        zzzeek
Date:        2013-07-06 22:42:18
Summary:     use "target tables" here

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/10c8867225f1/
Changeset:   10c8867225f1
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-06 22:42:44
Summary:     use "target tables" here

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/db68ecff12f7/
Changeset:   db68ecff12f7
Branch:      master
User:        zzzeek
Date:        2013-07-07 18:02:15
Summary:     remove undoc-members from query docstring [ticket:2774]

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/124db0eb91ec/
Changeset:   124db0eb91ec
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-07 18:02:51
Summary:     remove undoc-members from query docstring [ticket:2774]

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/31d43ae27557/
Changeset:   31d43ae27557
Branch:      None
User:        zzzeek
Date:        2013-07-07 20:28:24
Summary:     implement kw wrapping

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/57e8ec9d786d/
Changeset:   57e8ec9d786d
Branch:      ticket_2775
User:        zzzeek
Date:        2013-07-07 20:34:54
Summary:     support better looking "listen to this" targets

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/9f00c2cab922/
Changeset:   9f00c2cab922
Branch:      ticket_2775
User:        zzzeek
Date:        2013-07-08 19:39:21
Summary:     break out these tests

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/02a81707dc8b/
Changeset:   02a81707dc8b
Branch:      master
User:        zzzeek
Date:        2013-07-08 19:39:56
Summary:     - create a new system where we can decorate an event method
with @_legacy_signature, will inspect incoming listener functions
to see if they match an older signature, will wrap into a newer sig
- add an event listen argument named=True, will send all args as
kw args so that event listeners can be written with **kw, any combination
of names
- add a doc system to events that writes out the various calling styles
for a given event, produces deprecation messages automatically.
a little concerned that it's a bit verbose but will look at it up
on RTD for awhile to get a feel.
- change the calling signature for bulk update/delete events - we have
the BulkUD object right there, and there's at least six or seven things
people might want to see, so just send the whole BulkUD in
[ticket:2775]

Affected #:  12 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/fd55be01ddc0/
Changeset:   fd55be01ddc0
Branch:      master
User:        zzzeek
Date:        2013-07-11 21:15:09
Summary:     Dialect.initialize() is not called a second time if an :class:`.Engine`
is recreated, due to a disconnect error.   This fixes a particular
issue in the Oracle 8 dialect, but in general the dialect.initialize()
phase should only be once per dialect.  Also in 0.8.3. [ticket:2776]

Affected #:  6 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9a95a39b49a2/
Changeset:   9a95a39b49a2
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-11 21:16:34
Summary:     Dialect.initialize() is not called a second time if an :class:`.Engine`
is recreated, due to a disconnect error.   This fixes a particular
issue in the Oracle 8 dialect, but in general the dialect.initialize()
phase should only be once per dialect.  [ticket:2776]

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/1e332e03d394/
Changeset:   1e332e03d394
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-12 16:42:18
Summary:     don't split the regexps for chop_traceback()

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/269a166b73a8/
Changeset:   269a166b73a8
Branch:      master
User:        zzzeek
Date:        2013-07-12 16:42:53
Summary:     don't split the regexps for chop_traceback()

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/0ca7b53b4235/
Changeset:   0ca7b53b4235
Branch:      master
User:        zzzeek
Date:        2013-07-12 17:32:34
Summary:     Fixed bug where the expression system relied upon the ``str()``
form of a some expressions when referring to the ``.c`` collection
on a ``select()`` construct, but the ``str()`` form isn't available
since the element relies on dialect-specific compilation constructs,
notably the ``__getitem__()`` operator as used with a Postgresql
``ARRAY`` element.  The fix also adds a new exception class
:class:`.UnsupportedCompilationError` which is raised in those cases
where a compiler is asked to compile something it doesn't know
how to.  Also in 0.8.3.
[ticket:2780]

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/574dba8e61f5/
Changeset:   574dba8e61f5
Branch:      rel_0_8
User:        zzzeek
Date:        2013-07-12 17:33:24
Summary:     Fixed bug where the expression system relied upon the ``str()``
form of a some expressions when referring to the ``.c`` collection
on a ``select()`` construct, but the ``str()`` form isn't available
since the element relies on dialect-specific compilation constructs,
notably the ``__getitem__()`` operator as used with a Postgresql
``ARRAY`` element.  The fix also adds a new exception class
:class:`.UnsupportedCompilationError` which is raised in those cases
where a compiler is asked to compile something it doesn't know
how to.
[ticket:2780]

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.