sqlalchemy-commits — SVN commits logged to this list

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Quote URL tokens with semicolons for pyodbc, adodbapi

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f4ffd058ce5c/
Changeset:   f4ffd058ce5c
Branch:      rel_1_0
User:        zzzeek
Date:        2016-11-11 18:31:16+00:00
Summary:     Quote URL tokens with semicolons for pyodbc, adodbapi

Fixed bug in pyodbc dialect (as well as in the mostly non-working
adodbapi dialect) whereby a semicolon present in the password
or username fields could be interpreted as a separator for another
token; the values are now quoted when semicolons are present.

Change-Id: I5f99fd8db53ebf8e805e7d9d60bc09b8f1af603f
Fixes: #3762

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: zzzeek: Quote URL tokens with semicolons for pyodbc, adodbapi

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5fba7db9be7a/
Changeset:   5fba7db9be7a
Branch:      master
User:        zzzeek
Date:        2016-11-11 18:30:25+00:00
Summary:     Quote URL tokens with semicolons for pyodbc, adodbapi

Fixed bug in pyodbc dialect (as well as in the mostly non-working
adodbapi dialect) whereby a semicolon present in the password
or username fields could be interpreted as a separator for another
token; the values are now quoted when semicolons are present.

Change-Id: I5f99fd8db53ebf8e805e7d9d60bc09b8f1af603f
Fixes: #3762

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: zzzeek: - oragnize the changelog with tokens per .. change:: to allow

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/014bc5923770/
Changeset:   014bc5923770
Branch:      rel_1_0
User:        zzzeek
Date:        2016-11-11 17:04:37+00:00
Summary:      - oragnize the changelog with tokens per .. change:: to allow
   three way merges to succeed (hopefully). requires bump of changelog
   package.

Change-Id: Ia23b1754ad7e0841c6513647f0dd4987112a0511

Affected #:  2 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - oragnize the changelog with tokens per .. change:: to allow

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/91e7d46fe1dc/
Changeset:   91e7d46fe1dc
Branch:      None
User:        zzzeek
Date:        2016-11-11 17:03:13+00:00
Summary:     - oragnize the changelog with tokens per .. change:: to allow
three way merges to succeed (hopefully). requires bump of changelog
package.

Change-Id: Icd9bb7f4a4e01cc6ac66e8c7bb6631c3f6bb1d2c

Affected #:  3 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Use configured props for mapper.attrs, mapper.all_orm_descriptors

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8b64240e3a2c/
Changeset:   8b64240e3a2c
Branch:      rel_1_0
User:        zzzeek
Date:        2016-11-11 02:10:15+00:00
Summary:     Use configured props for mapper.attrs, mapper.all_orm_descriptors

Fixed bug where the :attr:`.Mapper.attrs`,
:attr:`.Mapper.all_orm_descriptors` and other derived attributes would
fail to refresh when mapper properties or other ORM constructs were
added to the mapper/class after these  accessors were first called.

Change-Id: Iaecdb4b3d8c3a3b44302a5880476e60a1f4e27d9
Fixes: #3778
(cherry picked from commit 6319eb0ce7c095ba7d4f60746ce12cf575730b46)

Affected #:  3 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Use configured props for mapper.attrs, mapper.all_orm_descriptors

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f2eb4aac9517/
Changeset:   f2eb4aac9517
Branch:      master
User:        zzzeek
Date:        2016-11-10 22:36:41+00:00
Summary:     Use configured props for mapper.attrs, mapper.all_orm_descriptors

Fixed bug where the :attr:`.Mapper.attrs`,
:attr:`.Mapper.all_orm_descriptors` and other derived attributes would
fail to refresh when mapper properties or other ORM constructs were
added to the mapper/class after these  accessors were first called.

(also trying different ways to get the changelog to merge cleanly)

Change-Id: Iaecdb4b3d8c3a3b44302a5880476e60a1f4e27d9
Fixes: #3778

Affected #:  3 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Consider version_id_prop when emitting bulk UPDATE

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e2a976e91657/
Changeset:   e2a976e91657
Branch:      rel_1_0
User:        zzzeek
Date:        2016-11-10 21:31:42+00:00
Summary:     Consider version_id_prop when emitting bulk UPDATE

The version id needs to be part of _changed_dict()
so that the value is present to send to
_emit_update_statements()

Change-Id: Ia85f0ef7714296a75cdc6c88674805afbbe752c8
Fixes: #3781

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/c9d8a67b52d1/
Changeset:   c9d8a67b52d1
Branch:      None
User:        zzzeek
Date:        2016-11-10 21:30:11+00:00
Summary:     Consider version_id_prop when emitting bulk UPDATE

The version id needs to be part of _changed_dict()
so that the value is present to send to
_emit_update_statements()

Change-Id: Ia85f0ef7714296a75cdc6c88674805afbbe752c8
Fixes: #3781

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/03429812125c/
Changeset:   03429812125c
Branch:      master
User:        zzzeek
Date:        2016-11-10 22:22:41+00:00
Summary:     Merge "Consider version_id_prop when emitting bulk UPDATE"
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: Kevin Jurczyk: Add conditional import for pysqlcipher3

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e81660d5c0ac/
Changeset:   e81660d5c0ac
Branch:      master
User:        Kevin Jurczyk
Date:        2016-11-10 21:29:16+00:00
Summary:     Add conditional import for pysqlcipher3

This is a Py3K supporting DBAPI for pysqlcipher.

Change-Id: I2a625274a371908f4de9d37f33e05408894b334b
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/320

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/ea934b95396d/
Changeset:   ea934b95396d
Branch:      None
User:        Benjamin Dopplinger
Date:        2016-11-10 16:19:09+00:00
Summary:     Remove non-working Connection.default_schema_name() method

The method `engine.base.Connection.default_schema_name` is broken since
4b532e2 (this was when `engine.dialect.get_default_schema_name` was
replaced with `engine.dialect.default_schema_name`).  The method is
unused and also is not functional for end-user use, so remove it
for now.

Change-Id: I6ffbd9ce1b9b54ff6df63ed45d7d33591f183933
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/321

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/33e277e856fe/
Changeset:   33e277e856fe
Branch:      master
User:        zzzeek
Date:        2016-11-10 20:30:04+00:00
Summary:     Merge "Remove non-working Connection.default_schema_name() method"
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: malor: Add support for server side cursors to mysqldb and pymysql

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d1e31ab1582e/
Changeset:   d1e31ab1582e
Branch:      master
User:        malor
Date:        2016-11-10 17:09:27+00:00
Summary:     Add support for server side cursors to mysqldb and pymysql

This allows to skip buffering of the results on the client side, e.g.
the following snippet:

    table = sa.Table(
        'testtbl', sa.MetaData(),
        sa.Column('id', sa.Integer, primary_key=True),
        sa.Column('a', sa.Integer),
        sa.Column('b', sa.String(512))
    )
    table.create(eng, checkfirst=True)

    with eng.connect() as conn:
        result = conn.execute(table.select().limit(1)).fetchone()
        if result is None:
            for _ in range(1000):
                conn.execute(
                    table.insert(),
                    [{'a': random.randint(1, 100000),
                      'b': ''.join(random.choice(string.ascii_letters) for _ in range(100))}
                      for _ in range(1000)]
                )

    with eng.connect() as conn:
        for row in conn.execution_options(stream_results=True).execute(table.select()):
            pass

now uses ~23 MB of memory instead of ~327 MB on CPython 3.5.2 and
PyMySQL 0.7.9.

psycopg2 implementation and execution options (stream_results,
server_side_cursors) are reused.

Change-Id: I4dc23ce3094f027bdff51b896b050361991c62e2

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.

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/6a688b736429/
Changeset:   6a688b736429
Branch:      master
User:        zzzeek
Date:        2016-11-10 16:08:52+00:00
Summary:     Ensure attribute keys used for bulk update pk set

Fixed bug in :meth:`.Session.bulk_update_mappings` where an alternate-named
primary key attribute would not track properly into the UPDATE statement.

Change-Id: I33e9140f45827772768fa548adcfeb4dbfc2208d
Fixes: #3849

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d31fddce8316/
Changeset:   d31fddce8316
Branch:      rel_1_0
User:        zzzeek
Date:        2016-11-10 16:10:38+00:00
Summary:     Ensure attribute keys used for bulk update pk set

Fixed bug in :meth:`.Session.bulk_update_mappings` where an alternate-named
primary key attribute would not track properly into the UPDATE statement.

Change-Id: I33e9140f45827772768fa548adcfeb4dbfc2208d
Fixes: #3849
(cherry picked from commit 6a688b736429e27a892bc02111414491fe4103b0)

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: Kevin Jurczyk: Add quotes around PRAGMA values in pysqlcipher connect.

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b141f9f3c8c5/
Changeset:   b141f9f3c8c5
Branch:      master
User:        Kevin Jurczyk
Date:        2016-11-08 17:16:57+00:00
Summary:     Add quotes around PRAGMA values in pysqlcipher connect.

Arguments such as cipher, kdf_iter, cipher_page_size and
cipher_use_hmac may (always?) require quotes within the
PRAGMA directive.

Change-Id: I2c808f34e1c44f0593b72b304e170e4af0a6035a
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/319

Affected #:  2 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Put include_table=True for DO UPDATE..WHERE, but not ON CONFLICT

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/942c2429c033/
Changeset:   942c2429c033
Branch:      master
User:        zzzeek
Date:        2016-11-08 03:03:16+00:00
Summary:     Put include_table=True for DO UPDATE..WHERE, but not ON CONFLICT

Fixed regression caused by the fix in :ticket:`3807` (version 1.1.0)
where we ensured that the tablename was qualified in the WHERE clause
of the DO UPDATE portion of PostgreSQL's ON CONFLICT, however you
*cannot* put the table name in the  WHERE clause in the actual ON
CONFLICT itself.   This was an incorrect assumption, so that portion
of the change in :ticket:`3807` is rolled back.

Change-Id: I442d8629496a8e405b54711cfcf487761810ae8a
Fixes: #3846
Fixes: #3807

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: zzzeek: Move setup functionality into _register_attribute

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c4a8afa4c6bf/
Changeset:   c4a8afa4c6bf
Branch:      master
User:        zzzeek
Date:        2016-11-06 17:46:28+00:00
Summary:     Move setup functionality into _register_attribute

Options like uselist and backref can be determined from
within _register_attribute based on parent_property
given; move this logic inside so that individual strategies
have less responsibility.  Also don't require that
_register_attribute consider the "strategy" itself
at all; it would be better if we could no longer require
that Joined/Subquery/etc loaders call upon the "lazy" strategy
in order to initialize attribute instrumentation and
this could be done more generically.

Fixes long-standing bug where the "noload" relationship loading
strategy would cause backrefs and/or back_populates options to be
ignored.   There is concern that some application that uses
"noload" might be surprised at a back-populating attribute
appearing suddenly, which may have side effects.  However,
"noload" itself must be extremely seldom used since as a
strategy, it already disables loading, population of attributes
is the only behavior that is even supported, so that this issue has existed
for at least through 0.7 four years ago without ever being
reported indicates extremely low use of this option.

Change-Id: Icffb9c83ac5782b76ce882ed1df4361a1efbfba3
Fixes: #3845

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: zzzeek: Add check for blank string coming from MySQL's enum

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/dd4e09d38729/
Changeset:   dd4e09d38729
Branch:      master
User:        zzzeek
Date:        2016-10-28 18:17:40+00:00
Summary:     Add check for blank string coming from MySQL's enum

MySQL's native ENUM type supports any non-valid value being sent, and
in response will return a blank string.  A hardcoded rule to check for
"is returning the blank string" has been added to the  MySQL
implementation for ENUM so that this blank string is returned to the
application rather than being rejected as a non-valid value.  Note that
if your MySQL enum is linking values to objects, you still get the
blank string back.

Change-Id: I61f85c20293a48b0c11a31f2a19f6756c206bd20
Fixes: #3841

Affected #:  3 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - 1.1.4 versioning

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/60b68ff4ee15/
Changeset:   60b68ff4ee15
Branch:      None
User:        zzzeek
Date:        2016-10-28 18:14:32+00:00
Summary:     - 1.1.4 versioning

Change-Id: I6545ebfeeee103cac133d0b8270a860cba2d2996

Affected #:  2 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: - 1.1.3

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2af8c1559776/
Changeset:   2af8c1559776
Branch:      None
User:        zzzeek
Date:        2016-10-27 14:47:26+00:00
Summary:     - 1.1.3

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/e56a9d85acd1/
Changeset:   e56a9d85acd1
Branch:      None
User:        zzzeek
Date:        2016-10-27 13:51:50+00:00
Summary:     Restore object to the identity_map upon delete() unconditionally

Fixed regression caused by :ticket:`2677` whereby calling
:meth:`.Session.delete` on an object that was already flushed as
deleted in that session would fail to set up the object in the
identity map (or reject the object), causing flush errors as the
object were in a state not accommodated by the unit of work.
The pre-1.1 behavior in this case has been restored, which is that
the object is put back into the identity map so that the DELETE
statement will be attempted again, which emits a warning that the number
of expected rows was not matched (unless the row were restored outside
of the session).

Change-Id: I9a8871f82cb1ebe67a7ad54d888d5ee835a9a40a
Fixes: #3839

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/3f1fe4e33c32/
Changeset:   3f1fe4e33c32
Branch:      master
User:        zzzeek
Date:        2016-10-27 14:46:15+00:00
Summary:     Merge "Restore object to the identity_map upon delete() unconditionally"
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/9974ab67f508/
Changeset:   9974ab67f508
Branch:      None
User:        Randy Barlow
Date:        2016-10-23 14:34:25+00:00
Summary:     Minor fixes in the ext.hybrid documentation.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/611f9e1b42ed/
Changeset:   611f9e1b42ed
Branch:      rel_1_0
User:        Randy Barlow
Date:        2016-10-27 14:42:09+00:00
Summary:     Minor fixes in the ext.hybrid documentation.

(cherry picked from commit 9974ab67f508a16423e8bc22122180b0bcdee807)

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: Ensure .mapper is set on _ColumnEntity

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1f32d014da5d/
Changeset:   1f32d014da5d
Branch:      master
User:        zzzeek
Date:        2016-10-21 14:42:14+00:00
Summary:     Ensure .mapper is set on _ColumnEntity

_ColumnEntity didn't seem to have .mapper present, which
due to the way _mapper_zero() worked didn't tend to come
across it.   With :ticket:`3608` _mapper_zero() has
been simplified so make sure this is now present.
Also ensure that _select_from_entity is an entity and
not a mapped class, though this does not seem to matter
at the moment.

Fixes: #3836

Change-Id: Id6dae8e700269b97de3b01562edee95ac1e01f80

Affected #:  3 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Don't set pg autoincrement if type affinity is not Integer

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/232eec47d139/
Changeset:   232eec47d139
Branch:      master
User:        zzzeek
Date:        2016-10-20 21:38:22+00:00
Summary:     Don't set pg autoincrement if type affinity is not Integer

Postgresql table reflection will ensure that the
:paramref:`.Column.autoincrement` flag is set to False when reflecting
a primary key column that is not of an :class:`.Integer` datatype,
even if the default is related to an integer-generating sequence.
This can happen if a column is created as SERIAL and the datatype
is changed.  The autoincrement flag can only be True if the datatype
is of integer affinity in the 1.1 series.

This bug is related to a test failure in downstream sqlalchemy_migrate.

Change-Id: I40260e47e1927a1ac940538408983c943bbdba28
Fixes: #3835

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/c97b1b822825/
Changeset:   c97b1b822825
Branch:      None
User:        zzzeek
Date:        2016-10-20 19:59:46+00:00
Summary:     Convert expression type for concat + Enum

Fixed bug involving new value translation and validation feature
in :class:`.Enum` whereby using the enum object in a string
concatenation would maintain the :class:`.Enum` type as the type
of the expression overall, producing missing lookups.  A string
concatenation against an :class:`.Enum`-typed column now uses
:class:`.String` as the datatype of the expression itself.

Change-Id: Id402054e3ef008e0250c740dbb7e1c80f339fe78
Fixes: #3833

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/78f2864b90c9/
Changeset:   78f2864b90c9
Branch:      master
User:        zzzeek
Date:        2016-10-20 20:37:00+00:00
Summary:     Merge "Convert expression type for concat + Enum"
Affected #:  3 files

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

--

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

[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Document Enum.enums is now a list

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/39d5a9726654/
Changeset:   39d5a9726654
Branch:      None
User:        zzzeek
Date:        2016-10-20 20:29:30+00:00
Summary:     Document Enum.enums is now a list

Change-Id: I27251c262f919df1b084cbb08759f672f05cd3f7
Fixes: #3834

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: Ensure TypeDecorator delegates _set_parent_with_dispatch

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/30bd28fca209/
Changeset:   30bd28fca209
Branch:      master
User:        zzzeek
Date:        2016-10-20 18:14:50+00:00
Summary:     Ensure TypeDecorator delegates _set_parent_with_dispatch

Ensure TypeDecorator delegates _set_parent_with_dispatch as well as
_set_parent to itself as well as its impl, as the TypeDecorator
class itself may have an active SchemaType implementation as well.

Fixed regression which occurred as a side effect of :ticket:`2919`,
which in the less typical case of a user-defined
:class:`.TypeDecorator` that was also itself an instance of
:class:`.SchemaType` (rather than the implementation being such)
would cause the column attachment events to be skipped for the
type itself.

Change-Id: I0afb498fd91ab7d948e4439e7323a89eafcce0bc
Fixes: #3832

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.