Thread: [Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets (Page 19)

Brought to you by: zzzeek

sqlalchemy-commits

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

From: Bitbucket <com...@bi...> - 2015-08-10 14:08:28

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/a7d7941d3eba/
Changeset:   a7d7941d3eba
Branch:      None
User:        zzzeek
Date:        2015-08-10 14:07:17+00:00
Summary:     - Fixed two issues regarding Sybase reflection, allowing tables
without primary keys to be reflected as well as ensured that
a SQL statement involved in foreign key detection is pre-fetched up
front to avoid driver issues upon nested queries.  Fixes here
courtesy Eugene Zapolsky; note that we cannot currently test
Sybase to locally verify these changes.
fixes #3508  fixes #3509

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/90327f6a9369/
Changeset:   90327f6a9369
Branch:      rel_1_0
User:        zzzeek
Date:        2015-08-10 14:07:54+00:00
Summary:     - Fixed two issues regarding Sybase reflection, allowing tables
without primary keys to be reflected as well as ensured that
a SQL statement involved in foreign key detection is pre-fetched up
front to avoid driver issues upon nested queries.  Fixes here
courtesy Eugene Zapolsky; note that we cannot currently test
Sybase to locally verify these changes.
fixes #3508  fixes #3509

(cherry picked from commit a7d7941d3ebafd16f603785c4677e371c675d1c0)

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

From: Bitbucket <com...@bi...> - 2015-08-10 17:21:54

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/020a7b643f25/
Changeset:   020a7b643f25
Branch:      None
User:        zzzeek
Date:        2015-08-10 14:06:27+00:00
Summary:     dev

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b150781220af/
Changeset:   b150781220af
Branch:      ticket_3499
User:        zzzeek
Date:        2015-08-10 17:21:17+00:00
Summary:     - most of the index model working, no tests yet
- ARRAY restored, most of JSON, not JSONB yet

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

From: Bitbucket <com...@bi...> - 2015-08-15 18:17:32

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1a7d60b0522c/
Changeset:   1a7d60b0522c
Branch:      None
User:        zzzeek
Date:        2015-08-15 17:56:29+00:00
Summary:     Merge branch 'master' into ticket_3499

Affected #:  20 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/fef58e7cb66b/
Changeset:   fef58e7cb66b
Branch:      ticket_3499
User:        zzzeek
Date:        2015-08-15 18:17:09+00:00
Summary:     - updates

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

From: Bitbucket <com...@bi...> - 2015-08-18 15:36:29

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ba1e959e5316/
Changeset:   ba1e959e5316
Branch:      None
User:        zzzeek
Date:        2015-08-18 15:33:56+00:00
Summary:     - document workaround type for ARRAY of ENUM, fixes #3467

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7a3a5e921132/
Changeset:   7a3a5e921132
Branch:      rel_1_0
User:        zzzeek
Date:        2015-08-18 15:35:26+00:00
Summary:     - document workaround type for ARRAY of ENUM, fixes #3467

(cherry picked from commit ba1e959e5316a8c17ca80dca950574038bd650c4)

Conflicts:
	lib/sqlalchemy/dialects/postgresql/array.py

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

From: Bitbucket <com...@bi...> - 2015-08-18 17:30:58

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/3f8f1f16bd9e/
Changeset:   3f8f1f16bd9e
Branch:      None
User:        zzzeek
Date:        2015-08-18 16:40:18+00:00
Summary:     - as the Concatenable mixin was changed to support calling down to
"super" instead of hardcoding to "self.type" for the default return
value, the base Comparator was returning other_comparator.type.   It's
not clear what the rationale for this was, though in theory the
base Comparator should possibly even throw an exception if the two
types aren't the same (or of the same affinity?) .
- mysql.SET was broken on this because the bitwise version adds "0"
to the value to force an integer within column_expression, we are doing type_coerces here
now in any case so that there is no type ambiguity for this
operation

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b653fedca5f0/
Changeset:   b653fedca5f0
Branch:      None
User:        zzzeek
Date:        2015-08-18 17:30:21+00:00
Summary:     - fix the postgresql_jsonb requirement to include the 9.4 requirement
- new test for json col['x']['y']['z'] seems to fail pre PG 9.4,
fails on comparisons for non-compatible data instead of not matching
- no need to call SpecPredicate(db) directly in exclusion functions,
by using Predicate.as_predicate() the spec strings can have version
comparisons

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

From: Bitbucket <com...@bi...> - 2015-08-18 22:05:58

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/ccaf38534049/
Changeset:   ccaf38534049
Branch:      None
User:        zzzeek
Date:        2015-08-18 21:39:39+00:00
Summary:     - test _instance_processor under cython

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/bb16e89674cd/
Changeset:   bb16e89674cd
Branch:      cython
User:        zzzeek
Date:        2015-08-18 22:05:04+00:00
Summary:     - teeny tiny things, we're saving almost nothing.   would need to
rewrite most everything in optimized pyx for this to be worth it.

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

From: Bitbucket <com...@bi...> - 2015-08-24 14:54:47

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/d57e5edbcdf9/
Changeset:   d57e5edbcdf9
Branch:      None
User:        zzzeek
Date:        2015-08-24 14:54:09+00:00
Summary:     - Fixed two issues in the "history_meta" example where history tracking
could encounter empty history, and where a column keyed to an alternate
attribute name would fail to track properly.  Fixes courtesy
Alex Fraser.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4bd1c615af12/
Changeset:   4bd1c615af12
Branch:      rel_1_0
User:        zzzeek
Date:        2015-08-24 14:54:25+00:00
Summary:     - Fixed two issues in the "history_meta" example where history tracking
could encounter empty history, and where a column keyed to an alternate
attribute name would fail to track properly.  Fixes courtesy
Alex Fraser.

(cherry picked from commit d57e5edbcdf915168c613cdd6da0bd7bea877fa4)

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

From: Bitbucket <com...@bi...> - 2015-08-24 16:50:16

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/3e220ecb9e10/
Changeset:   3e220ecb9e10
Branch:      None
User:        zzzeek
Date:        2015-08-24 16:04:38+00:00
Summary:     - test for no column affinity as well

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/b60cd22f4e84/
Changeset:   b60cd22f4e84
Branch:      ticket_3216
User:        zzzeek
Date:        2015-08-24 16:41:27+00:00
Summary:     - work out a system of raising at the compiler level when we see an
insert() statement going in where a column in the primary key is
going to be NULL, due to no defaults or autoincrement set up.
The rationale here is to attempt to make it completely clear
if we decide that we are going to make this change hard in 1.1.
It does appear that there are a lot of tests in the PG dialect that
were having to guess between multiple failure modes for Postgresql
DBAPIs whereas now we have a consistent message, so that is an improvement.
Still concerning is that an application that upgrades to 1.1
and then does a schema create, will also create a schema that doesn't
have autoincrement set up; they won't get this error message until
insert time.  User would need to be savvy enough to recreate the tables.

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

From: Bitbucket <com...@bi...> - 2015-08-27 14:35:38

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5295a683f9ac/
Changeset:   5295a683f9ac
Branch:      None
User:        zzzeek
Date:        2015-08-27 14:32:21+00:00
Summary:     - add PG-specific aggregate_order_by(), references #3132

Affected #:  7 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e2209f753425/
Changeset:   e2209f753425
Branch:      None
User:        zzzeek
Date:        2015-08-27 14:33:21+00:00
Summary:     - consolidate "constraints.py" into the more general "ext.py",
for all assorted PG SQL extensions

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

From: Bitbucket <com...@bi...> - 2015-08-31 15:30:52

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/c39ff9978dbb/
Changeset:   c39ff9978dbb
Branch:      None
User:        zzzeek
Date:        2015-08-31 15:30:03+00:00
Summary:     - Fixed regression in 1.0-released default-processor for multi-VALUES
insert statement, :ticket:`3288`, where the column type for the
default-holding column would not be propagated to the compiled
statement in the case where the default was being used,
leading to bind-level type handlers not being invoked.
fixes #3520

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/161209c70add/
Changeset:   161209c70add
Branch:      rel_1_0
User:        zzzeek
Date:        2015-08-31 15:30:21+00:00
Summary:     - Fixed regression in 1.0-released default-processor for multi-VALUES
insert statement, :ticket:`3288`, where the column type for the
default-holding column would not be propagated to the compiled
statement in the case where the default was being used,
leading to bind-level type handlers not being invoked.
fixes #3520

(cherry picked from commit c39ff9978dbb77cbea4f1ee08234887d8aa1b165)

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

From: Bitbucket <com...@bi...> - 2015-09-01 18:54:44

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/dca6e7f1ef4a/
Changeset:   dca6e7f1ef4a
Branch:      None
User:        zzzeek
Date:        2015-09-01 17:26:20+00:00
Summary:     - experiment with not having the identity map check run twice

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/5df2f0346c49/
Changeset:   5df2f0346c49
Branch:      ticket_2677
User:        zzzeek
Date:        2015-09-01 18:54:20+00:00
Summary:     - get all events to actually work

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

From: Bitbucket <com...@bi...> - 2015-09-01 21:53:40

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/627931b09ae4/
Changeset:   627931b09ae4
Branch:      None
User:        zzzeek
Date:        2015-09-01 20:04:43+00:00
Summary:     - add new documentation that applies to all modern SQLA versions,
detailing ORM event recipes across the board.

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4ae09ba907fe/
Changeset:   4ae09ba907fe
Branch:      ticket_2677
User:        zzzeek
Date:        2015-09-01 21:53:18+00:00
Summary:     - implement session lifecycle events

Affected #:  13 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

From: Bitbucket <com...@bi...> - 2015-09-01 22:35:29

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/52996c610db8/
Changeset:   52996c610db8
Branch:      None
User:        zzzeek
Date:        2015-09-01 22:28:07+00:00
Summary:     - add new documentation that applies to all modern SQLA versions,
detailing ORM event recipes across the board.

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4895fad11898/
Changeset:   4895fad11898
Branch:      ticket_2677
User:        zzzeek
Date:        2015-09-01 22:35:00+00:00
Summary:     - implement session lifecycle events

Affected #:  14 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

From: Bitbucket <com...@bi...> - 2015-09-02 21:23:08

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8be93c23ee56/
Changeset:   8be93c23ee56
Branch:      None
User:        zzzeek
Date:        2015-09-02 15:58:59+00:00
Summary:     - add new documentation that applies to all modern SQLA versions,
detailing ORM event recipes across the board.

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e7579a89c792/
Changeset:   e7579a89c792
Branch:      None
User:        zzzeek
Date:        2015-09-02 18:51:39+00:00
Summary:     - implement session lifecycle events

Affected #:  15 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

From: Bitbucket <com...@bi...> - 2015-09-08 17:02:31

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/68a6701c6d72/
Changeset:   68a6701c6d72
Branch:      None
User:        zzzeek
Date:        2015-09-08 17:00:26+00:00
Summary:     - Fixed bug in :meth:`.Session.bulk_save_objects` where a mapped
column that had some kind of "fetch on update" value and was not
locally present in the given object would cause an AttributeError
within the operation.
fixes #3525

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/55ec07c46c33/
Changeset:   55ec07c46c33
Branch:      rel_1_0
User:        zzzeek
Date:        2015-09-08 17:01:08+00:00
Summary:     - Fixed bug in :meth:`.Session.bulk_save_objects` where a mapped
column that had some kind of "fetch on update" value and was not
locally present in the given object would cause an AttributeError
within the operation.
fixes #3525

(cherry picked from commit 68a6701c6d72d6c6ef1ea2b7d615273659e8b735)

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

From: Bitbucket <com...@bi...> - 2015-09-08 22:11:04

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2fb3bb31ef89/
Changeset:   2fb3bb31ef89
Branch:      None
User:        bsmithgall
Date:        2015-09-08 01:37:19+00:00
Summary:     fix typo in session events docs

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/f5b13797a633/
Changeset:   f5b13797a633
Branch:      master
User:        zzzeek
Date:        2015-09-08 22:10:51+00:00
Summary:     Merged in bsmithgall/sqlalchemy/event-doc-link-fix (pull request #60)

fix typo in session events 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

From: Bitbucket <com...@bi...> - 2015-09-08 22:12:10

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/0d5a2155f0e1/
Changeset:   0d5a2155f0e1
Branch:      rel_1_0
User:        bsmithgall
Date:        2015-09-08 22:11:45+00:00
Summary:     fix typo in session events docs

(cherry picked from commit 2fb3bb31ef897ee48748908524288067c53df4e1)

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/0bf88b71bcef/
Changeset:   0bf88b71bcef
Branch:      rel_0_9
User:        bsmithgall
Date:        2015-09-08 22:11:51+00:00
Summary:     fix typo in session events docs

(cherry picked from commit 2fb3bb31ef897ee48748908524288067c53df4e1)

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

From: Bitbucket <com...@bi...> - 2015-09-23 20:41:03

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/47fcb1d0b6ad/
Changeset:   47fcb1d0b6ad
Branch:      None
User:        zzzeek
Date:        2015-09-23 20:40:16+00:00
Summary:     - Fixed rare TypeError which could occur when stringifying certain
kinds of internal column loader options within internal logging.
fixes #3539

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/560d20f00388/
Changeset:   560d20f00388
Branch:      rel_1_0
User:        zzzeek
Date:        2015-09-23 20:40:42+00:00
Summary:     - Fixed rare TypeError which could occur when stringifying certain
kinds of internal column loader options within internal logging.
fixes #3539

(cherry picked from commit 47fcb1d0b6ad6481e89d4b2e8c2cc29cf7c03d8b)

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

From: Bitbucket <com...@bi...> - 2015-09-24 19:32:51

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/91255618ddb4/
Changeset:   91255618ddb4
Branch:      None
User:        Eric Siegerman
Date:        2015-09-24 19:25:15+00:00
Summary:     Fix sqlalchemy.ext.baked.Result.one_or_none() exception message

Also add a couple of missing tests.
Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/bdac0369b2d0/
Changeset:   bdac0369b2d0
Branch:      rel_1_0
User:        Eric Siegerman
Date:        2015-09-24 19:32:31+00:00
Summary:     Fix sqlalchemy.ext.baked.Result.one_or_none() exception message

Also add a couple of missing tests.
(cherry picked from commit 91255618ddb47553774c620a23479adf88c27b74)

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

From: Bitbucket <com...@bi...> - 2015-10-05 13:50:43

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4578ab54a5b8/
Changeset:   4578ab54a5b8
Branch:      None
User:        zzzeek
Date:        2015-10-05 13:49:34+00:00
Summary:     - Fixed bug in Oracle dialect where reflection of tables and other
symbols with names quoted to force all-lower-case would not be
identified properly in reflection queries.  The :class:`.quoted_name`
construct is now applied to incoming symbol names that detect as
forced into all-lower-case within the "name normalize" process.
fixes #3548

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/0b8489f70f13/
Changeset:   0b8489f70f13
Branch:      rel_1_0
User:        zzzeek
Date:        2015-10-05 13:50:09+00:00
Summary:     - Fixed bug in Oracle dialect where reflection of tables and other
symbols with names quoted to force all-lower-case would not be
identified properly in reflection queries.  The :class:`.quoted_name`
construct is now applied to incoming symbol names that detect as
forced into all-lower-case within the "name normalize" process.
fixes #3548

(cherry picked from commit 4578ab54a5b849fdb94a7032987f105b7ec117a4)

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

From: Bitbucket <com...@bi...> - 2015-10-07 14:05:16

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/61fc1d07160b/
Changeset:   61fc1d07160b
Branch:      ticket_3216
User:        zzzeek
Date:        2015-10-07 14:01:35+00:00
Summary:     - tweaks

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/414af7b61291/
Changeset:   414af7b61291
Branch:      None
User:        zzzeek
Date:        2015-10-07 14:02:45+00:00
Summary:     - The system by which a :class:`.Column` considers itself to be an
"auto increment" column has been changed, such that autoincrement
is no longer implicitly enabled for a :class:`.Table` that has a
composite primary key.  In order to accommodate being able to enable
autoincrement for a composite PK member column while at the same time
maintaining SQLAlchemy's long standing behavior of enabling
implicit autoincrement for a single integer primary key, a third
state has been added to the :paramref:`.Column.autoincrement` parameter
``"auto"``, which is now the default. fixes #3216
- The MySQL dialect no longer generates an extra "KEY" directive when
generating CREATE TABLE DDL for a table using InnoDB with a
composite primary key with AUTO_INCREMENT on a column that isn't the
first column;  to overcome InnoDB's limitation here, the PRIMARY KEY
constraint is now generated with the AUTO_INCREMENT column placed
first in the list of columns.

Affected #:  22 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

From: Bitbucket <com...@bi...> - 2015-10-09 21:08:23

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/febe0c0faae6/
Changeset:   febe0c0faae6
Branch:      None
User:        Eric Siegerman
Date:        2015-09-28 16:12:27+00:00
Summary:     Doc fix

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/2ef7c5e49990/
Changeset:   2ef7c5e49990
Branch:      None
User:        zzzeek
Date:        2015-10-09 21:07:52+00:00
Summary:     Merge remote-tracking branch 'origin/pr/205'

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

From: Bitbucket <com...@bi...> - 2015-10-09 21:12:23

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/2e5e6ff96cc9/
Changeset:   2e5e6ff96cc9
Branch:      None
User:        Eric Siegerman
Date:        2015-09-28 16:08:19+00:00
Summary:     Remplement Query.one() in terms of .one_or_none()

Thanks to Mike Bayer for suggesting a simpler refactoring.
Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/78a7bbdb3b09/
Changeset:   78a7bbdb3b09
Branch:      None
User:        zzzeek
Date:        2015-10-09 21:11:56+00:00
Summary:     Merge remote-tracking branch 'origin/pr/203'

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

From: Bitbucket <com...@bi...> - 2015-10-09 22:02:38

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/9d08c6abc21d/
Changeset:   9d08c6abc21d
Branch:      None
User:        zzzeek
Date:        2015-10-09 22:01:43+00:00
Summary:     - Added the :paramref:`.AssociationProxy.info` parameter to the
:class:`.AssociationProxy` constructor, to suit the
:attr:`.AssociationProxy.info` accessor that was added in
:ticket:`2971`.  This is possible because :class:`.AssociationProxy`
is constructed explicitly, unlike a hybrid which is constructed
implicitly via the decorator syntax.
fixes #3551

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/b63229aebe8d/
Changeset:   b63229aebe8d
Branch:      rel_1_0
User:        zzzeek
Date:        2015-10-09 22:02:19+00:00
Summary:     - Added the :paramref:`.AssociationProxy.info` parameter to the
:class:`.AssociationProxy` constructor, to suit the
:attr:`.AssociationProxy.info` accessor that was added in
:ticket:`2971`.  This is possible because :class:`.AssociationProxy`
is constructed explicitly, unlike a hybrid which is constructed
implicitly via the decorator syntax.
fixes #3551

(cherry picked from commit 9d08c6abc21dcf3d832897d38aaba84aeaa14fa6)

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

From: Bitbucket <com...@bi...> - 2015-10-19 16:18:25

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/1e0afd584c12/
Changeset:   1e0afd584c12
Branch:      None
User:        zzzeek
Date:        2015-10-19 16:17:37+00:00
Summary:     - Fixed regression in 1.0 where new feature of using "executemany"
for UPDATE statements in the ORM (e.g. :ref:`feature_updatemany`)
would break on Postgresql and other RETURNING backends
when using server-side version generation
schemes, as the server side value is retrieved via RETURNING which
is not supported with executemany.
fixes #3556

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4f54607923a1/
Changeset:   4f54607923a1
Branch:      rel_1_0
User:        zzzeek
Date:        2015-10-19 16:18:02+00:00
Summary:     - Fixed regression in 1.0 where new feature of using "executemany"
for UPDATE statements in the ORM (e.g. :ref:`feature_updatemany`)
would break on Postgresql and other RETURNING backends
when using server-side version generation
schemes, as the server side value is retrieved via RETURNING which
is not supported with executemany.
fixes #3556

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.

<< < 1 .. 17 18 19 20 21 .. 30 > >> (Page 19 of 30)