sqlalchemy-commits — SVN commits logged to this list

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

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b04dd5ee2f5b/
Changeset:   b04dd5ee2f5b
Branch:      ticket_3516
User:        zzzeek
Date:        2015-08-24 21:57:36+00:00
Summary:     - wip

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

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

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

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

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: zzzeek: - repair the inspection hook in sqltypes to not be fooled

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/03e47a825547/
Changeset:   03e47a825547
Branch:      None
User:        zzzeek
Date:        2015-08-22 20:01:23+00:00
Summary:     - repair the inspection hook in sqltypes to not be fooled
by mock and other __getattr__ impostors

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: - Added new checks for the common error case of passing mapped classes

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8712ef2f8149/
Changeset:   8712ef2f8149
Branch:      None
User:        zzzeek
Date:        2015-08-22 16:47:13+00:00
Summary:     - Added new checks for the common error case of passing mapped classes
or mapped instances into contexts where they are interpreted as
SQL bound parameters; a new exception is raised for this.
fixes #3321

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: 3 new changesets

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

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e0a8030048f4/
Changeset:   e0a8030048f4
Branch:      None
User:        zzzeek
Date:        2015-08-21 20:36:15+00:00
Summary:     - rework the "controlling DDL sequences" documentation to
refer mostly to the DDL object; this system is primarily useful
in that case, and not for built-in objects.  Reference that
the built-in case is not really viable right now. References #3442.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/2759ec3e8a3a/
Changeset:   2759ec3e8a3a
Branch:      rel_1_0
User:        zzzeek
Date:        2015-08-21 20:37:17+00:00
Summary:     - rework the "controlling DDL sequences" documentation to
refer mostly to the DDL object; this system is primarily useful
in that case, and not for built-in objects.  Reference that
the built-in case is not really viable right now. References #3442.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/f71596bdd576/
Changeset:   f71596bdd576
Branch:      rel_0_9
User:        zzzeek
Date:        2015-08-21 20:37:21+00:00
Summary:     - rework the "controlling DDL sequences" documentation to
refer mostly to the DDL object; this system is primarily useful
in that case, and not for built-in objects.  Reference that
the built-in case is not really viable right now. References #3442.

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: - new approach to autoincrement, towards references #3216

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8f81f07917a7/
Changeset:   8f81f07917a7
Branch:      ticket_3216
User:        zzzeek
Date:        2015-08-21 19:35:00+00:00
Summary:     - new approach to autoincrement, towards references #3216
- We add a new value of "autoincrement" called "auto".  This is now the
default for all columns, no longer True.
- the work of determining _autoincrement_column now moves to
PrimaryKeyConstraint itself, as "autoincrement" is explictly a pk-only
concept
- pkc detects autoincrement at the same time Table did, based on memoized_property.
attempts to make this a more "active" setting are more complicated because
during table construction with or without reflection the columns within the
pkc are in flux and determiniations can't really be made without
looking at all columns.
- with the difference between "auto" and True, we now can add validation
rules when True is set:  1. only one column may have autoincrement=True
2. autoincrement=True *requires* an Integer type, error is raised otherwise
3. column default has to be None or a Sequence 4. column server_default has
to be None or server-reflected
- when autoincrement=True is not set, we're looking for autoincrement='auto'.
We only care about 'auto' when there is *only one column in the PK*.  E.g.
we no longer set *any* column to "autoincrement" implicitly if the key
is composite, this requires "autoincrement=True".  This is the core of
- we get rid of the awkward rule that we create "KEY idx_autoinc_foo"
for a MySQL InnoDB column that is explicit autoincrement in a composite
PK and not the first column.  that was a terrible idea.  when the
non-first column in a composite PK is autoincrement=True, *we render it
first in the PRIMARY KEY constraint*.  Problem solved, no more implicit
index, no more guessing if we're innodb (this guess was wrong in the case
of innodb set on the server anyway).  this is again a proposal for a big
change in behavior; positives include that a surprise KEY is no longer
created, won't show up in alembic autogen and generates a more
efficient structure.
- databases where "autoincrement" is entirely implicit, e.g. SQLite,
should raise an error now when autoincrement=True is set and can't
be satisfied; SQLite dialect now raises this if autoincrement=True
on a composite primary key since SQLite never does this (note
that as always, this is distinct from SQLite's "sqlite_autoincrement"
keyword which we support distinctly).

Affected #:  7 files

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

--

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

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

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

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/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: zzzeek: - some cleanups in compiler.py

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/acda2e7d0b73/
Changeset:   acda2e7d0b73
Branch:      None
User:        zzzeek
Date:        2015-08-18 21:25:05+00:00
Summary:     - some cleanups in compiler.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: zzzeek: - forgot to implement py3k logic for JSON.NULL

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/871330c37907/
Changeset:   871330c37907
Branch:      None
User:        zzzeek
Date:        2015-08-18 20:36:56+00:00
Summary:     - forgot to implement py3k logic for JSON.NULL

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: - fix missing ANY symbol

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/9fd31d062f66/
Changeset:   9fd31d062f66
Branch:      rel_0_9
User:        zzzeek
Date:        2015-08-18 17:37:01+00:00
Summary:     - fix missing ANY symbol

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/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

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

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: 5 new changesets

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

5 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/74a43ee08b34/
Changeset:   74a43ee08b34
Branch:      None
User:        zzzeek
Date:        2015-08-17 19:43:14+00:00
Summary:     Merge branch 'ticket_3499' into ticket_3514

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/072a1f716ee9/
Changeset:   072a1f716ee9
Branch:      None
User:        zzzeek
Date:        2015-08-17 20:27:33+00:00
Summary:     - doc updates
- test fixes

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d0291319eeb3/
Changeset:   d0291319eeb3
Branch:      ticket_3514
User:        zzzeek
Date:        2015-08-17 20:43:31+00:00
Summary:     - changelogs

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ceeb033054f0/
Changeset:   ceeb033054f0
Branch:      None
User:        zzzeek
Date:        2015-08-17 21:07:10+00:00
Summary:     - merge of ticket_3499 indexed access branch
- The "hashable" flag on special datatypes such as :class:`.postgresql.ARRAY`,
:class:`.postgresql.JSON` and :class:`.postgresql.HSTORE` is now
set to False, which allows these types to be fetchable in ORM
queries that include entities within the row.  fixes #3499
- The Postgresql :class:`.postgresql.ARRAY` type now supports multidimensional
indexed access, e.g. expressions such as ``somecol[5][6]`` without
any need for explicit casts or type coercions, provided
that the :paramref:`.postgresql.ARRAY.dimensions` parameter is set to the
desired number of dimensions. fixes #3487
- The return type for the :class:`.postgresql.JSON` and :class:`.postgresql.JSONB`
when using indexed access has been fixed to work like Postgresql itself,
and returns an expression that itself is of type :class:`.postgresql.JSON`
or :class:`.postgresql.JSONB`.  Previously, the accessor would return
:class:`.NullType` which disallowed subsequent JSON-like operators to be
used. part of fixes #3503
- The :class:`.postgresql.JSON`, :class:`.postgresql.JSONB` and
:class:`.postgresql.HSTORE` datatypes now allow full control over the
return type from an indexed textual access operation, either ``column[someindex].astext``
for a JSON type or ``column[someindex]`` for an HSTORE type,
via the :paramref:`.postgresql.JSON.astext_type` and
:paramref:`.postgresql.HSTORE.text_type` parameters. also part of fixes #3503
- The :attr:`.postgresql.JSON.Comparator.astext` modifier no longer
calls upon :meth:`.ColumnElement.cast` implicitly, as PG's JSON/JSONB
types allow cross-casting between each other as well.  Code that
makes use of :meth:`.ColumnElement.cast` on JSON indexed access,
e.g. ``col[someindex].cast(Integer)``, will need to be changed
to call :attr:`.postgresql.JSON.Comparator.astext` explicitly.  This is
part of the refactor in references #3503 for consistency in operator
use.

Affected #:  24 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d14a4b480c3b/
Changeset:   d14a4b480c3b
Branch:      None
User:        zzzeek
Date:        2015-08-17 21:12:16+00:00
Summary:     - merge of ticket_3514 None-handling branch
- Fixes to the ORM and to the postgresql JSON type regarding the
``None`` constant in conjunction with the Postgresql :class:`.JSON` type.  When
the :paramref:`.JSON.none_as_null` flag is left at its default
value of ``False``, the ORM will now correctly insert the Json
"'null'" string into the column whenever the value on the ORM
object is set to the value ``None`` or when the value ``None``
is used with :meth:`.Session.bulk_insert_mappings`,
**including** if the column has a default or server default on it.  This
makes use of a new type-level flag "evaluates_none" which is implemented
by the JSON type based on the none_as_null flag. fixes #3514
- Added a new constant :attr:`.postgresql.JSON.NULL`, indicating
that the JSON NULL value should be used for a value
regardless of other settings. part of fixes #3514

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: zzzeek: - make sure we maintain the has_mapper_entities flag

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e6ab7a5ff5f1/
Changeset:   e6ab7a5ff5f1
Branch:      ticket_3499
User:        zzzeek
Date:        2015-08-17 19:24:41+00:00
Summary:     - make sure we maintain the has_mapper_entities flag

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: - Additional fixes have been made regarding the value of ``None``

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/5215d96d2886/
Changeset:   5215d96d2886
Branch:      ticket_3514
User:        zzzeek
Date:        2015-08-17 19:14:19+00:00
Summary:     - Additional fixes have been made regarding the value of ``None``
in conjunction with the Postgresql :class:`.JSON` type.  When
the :paramref:`.JSON.none_as_null` flag is left at its default
value of ``False``, the ORM will now correctly insert the Json
"'null'" string into the column whenever the value on the ORM
object is set to the value ``None`` or when the value ``None``
is used with :meth:`.Session.bulk_insert_mappings`,
**including** if the column has a default or server default on it.
fixes #3514
- Added a new constant :attr:`.postgresql.JSON.NULL`, indicating
that the JSON NULL value should be used for a value
regardless of other settings.

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/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: zzzeek: - correct this, need brackets

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/10cacef2c0e0/
Changeset:   10cacef2c0e0
Branch:      master
User:        zzzeek
Date:        2015-08-15 17:54:59+00:00
Summary:     - correct this, need brackets

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: - make these failure cases more specific to catch Oracle.

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/e1129b2d3e21/
Changeset:   e1129b2d3e21
Branch:      master
User:        zzzeek
Date:        2015-08-15 17:53:38+00:00
Summary:     - make these failure cases more specific to catch Oracle.
Would be nice to fix Oracle here

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: 3 new changesets

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

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b00b430e8751/
Changeset:   b00b430e8751
Branch:      None
User:        zzzeek
Date:        2015-08-14 19:34:01+00:00
Summary:     - add tests for InstanceEvents.init, InstanceEvents.init_failure
- ensure that kwargs can be modified in-place within InstanceEvents.init
and that these take effect for the __init__ method.
- improve documentation for these and related events, including
that kwargs can be modified in-place.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/42281066ca82/
Changeset:   42281066ca82
Branch:      rel_1_0
User:        zzzeek
Date:        2015-08-14 19:34:57+00:00
Summary:     - add tests for InstanceEvents.init, InstanceEvents.init_failure
- ensure that kwargs can be modified in-place within InstanceEvents.init
and that these take effect for the __init__ method.
- improve documentation for these and related events, including
that kwargs can be modified in-place.

(cherry picked from commit b00b430e87512d721ad30c81fdcb35a5253dfc0a)

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/4377f345c6c7/
Changeset:   4377f345c6c7
Branch:      rel_0_9
User:        zzzeek
Date:        2015-08-14 19:35:02+00:00
Summary:     - add tests for InstanceEvents.init, InstanceEvents.init_failure
- ensure that kwargs can be modified in-place within InstanceEvents.init
and that these take effect for the __init__ method.
- improve documentation for these and related events, including
that kwargs can be modified in-place.

(cherry picked from commit b00b430e87512d721ad30c81fdcb35a5253dfc0a)

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: dstufft: Tell Wheel to generate platform and interpreter specific wheels

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/39517d10466e/
Changeset:   39517d10466e
Branch:      None
User:        dstufft
Date:        2015-08-13 18:57:53+00:00
Summary:     Tell Wheel to generate platform and interpreter specific wheels

By telling wheel that we have extension modules, even though we
have none, wheel will create a Wheel which is platform and
interpreter specific. This will ensure that the pure Python wheels
on PyPy do not trigger installs on CPython without the C speedups.

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: - we can again use setuptools.find_packages since we require setuptools

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/44420423de34/
Changeset:   44420423de34
Branch:      master
User:        zzzeek
Date:        2015-08-13 18:48:18+00:00
Summary:     - we can again use setuptools.find_packages since we require setuptools
- clean up other things we aren't using anymore

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: - The behavior of the :func:`.union` construct and related constructs

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/88749550f6b9/
Changeset:   88749550f6b9
Branch:      None
User:        zzzeek
Date:        2015-08-12 18:26:11+00:00
Summary:     - The behavior of the :func:`.union` construct and related constructs
such as :meth:`.Query.union` now handle the case where the embedded
SELECT statements need to be parenthesized due to the fact that they
include LIMIT, OFFSET and/or ORDER BY.   These queries **do not work
on SQLite**, and will fail on that backend as they did before, but
should now work on all other backends.
fixes #2528

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: zzzeek: - add tests for array both in PG as well as generic Indexable;

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/b5a823bedefc/
Changeset:   b5a823bedefc
Branch:      ticket_3499
User:        zzzeek
Date:        2015-08-11 22:03:53+00:00
Summary:     - add tests for array both in PG as well as generic Indexable;
add compilation tests for all PG ARRAY operators

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: - add tests for hashable flag, references #3499

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/f657d4283b74/
Changeset:   f657d4283b74
Branch:      ticket_3499
User:        zzzeek
Date:        2015-08-11 21:35:33+00:00
Summary:     - add tests for hashable flag, references #3499

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.