delta/python-packages/sqlalchemy.git/lib/sqlalchemy, branch pr/315 github.com: zzzeek/sqlalchemy.git Remove some legacy dead code from the declared_attr logic 2016-10-16T14:45:54+00:00 Pierre Jaury pierre@jaury.eu 2016-10-16T14:45:54+00:00 d18221c542bf4d7381be2afdcd4c098698ff8eae The second 'if' condition was never called because the original condition always returns. 
The second 'if' condition was never called because the original
condition always returns.
- setup for next version 2016-10-13T16:27:51+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-10-13T16:27:51+00:00 6b7b77896dd296b3891bc67a774c4cb2e1236902 Change-Id: I4a7ef54bec3891821954061a9b4ed19d398989f3 
Change-Id: I4a7ef54bec3891821954061a9b4ed19d398989f3
Update the Column.nullable docstring for the primary_key=True case 2016-10-10T15:54:04+00:00 Matt Riedemann mriedem@us.ibm.com 2016-10-10T15:43:07+00:00 4b94ee113baab901aee881ad94851587c912f785 While reviewing a change that created a new table, the primary_key column value was set to True but nullable was not explicitly set, which led to some confusion over the default behavior for the nullable column value when setting a primary_key. Looking at the docs it's not clear, but the code shows that if nullable is not specified, then nullable = not primary_key, so nullable defaults to False when primary_key is True. This patch adds a simple clarification to the docs so people don't have to check the code. Change-Id: I8553339d56fbae11370c7c6af6d8d4723163be1c Pull-request: https://github.com/zzzeek/sqlalchemy/pull/312 
While reviewing a change that created a new table, the
primary_key column value was set to True but nullable was not
explicitly set, which led to some confusion over the default
behavior for the nullable column value when setting a primary_key.

Looking at the docs it's not clear, but the code shows that if
nullable is not specified, then nullable = not primary_key, so
nullable defaults to False when primary_key is True.

This patch adds a simple clarification to the docs so people
don't have to check the code.

Change-Id: I8553339d56fbae11370c7c6af6d8d4723163be1c
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/312
spelling: Postgresql -> PostgreSQL 2016-10-08T17:42:50+00:00 Ville Skyttä ville.skytta@iki.fi 2016-10-07T10:18:58+00:00 8c2c464cb8e1b40f90f544295afbf9a83b372eb7 






Spelling fixes
2016-10-08T17:42:50+00:00

Ville Skyttä
ville.skytta@iki.fi

2016-10-07T10:06:09+00:00

e47063bfe0de1318c12a4f9ef67b9538cad34489












Change autoincrement compileerror to a warning
2016-10-07T13:54:39+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-10-07T13:05:34+00:00

8a13957db790c77b76c11f5f43fad1492a50fcf0

Users are complaining that IntegrityError is no longer
raised.

Change-Id: I0855d5b7a98d4338f0910501b6e6d404ba33634d
Fixes: #3216





Users are complaining that IntegrityError is no longer
raised.

Change-Id: I0855d5b7a98d4338f0910501b6e6d404ba33634d
Fixes: #3216







Catch DBAPIError instead of ProgrammingError for pyodbc fail
2016-10-07T13:17:46+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-10-07T13:16:22+00:00

ae9300cac0ec398f92d9e523273403126a709134

Change-Id: Ide9e916d02fbbef549aa2838d1402c2b091e701d
Fixes: #3820





Change-Id: Ide9e916d02fbbef549aa2838d1402c2b091e701d
Fixes: #3820







- set up for 1.1.1
2016-10-06T02:31:31+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-10-06T02:31:31+00:00

b1fe748feafd83e256af01766d703ae5d552a413

Change-Id: I569a03a6e86aa096be6744ecb479fe8485f7def6





Change-Id: I569a03a6e86aa096be6744ecb479fe8485f7def6







Propagate execution_options at compile stage
2016-10-05T20:47:31+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-10-05T17:59:58+00:00

71030d67bd7c7948ef4a4d868821703ef5a57476

Compiler can now set up execution options and additionally
will propagate autocommit from embedded CTEs.

Change-Id: I19db7b8fe4d84549ea95342e8d2040189fed1bbe
Fixes: #3805





Compiler can now set up execution options and additionally
will propagate autocommit from embedded CTEs.

Change-Id: I19db7b8fe4d84549ea95342e8d2040189fed1bbe
Fixes: #3805







Check for __clause_element__() in ORM insert/update
2016-10-05T16:11:53+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-10-05T14:57:30+00:00

09b685b24b19636e11169c181b45333f9739ca35

ORM attributes can now be assigned any object that is has a
``__clause_element__()`` attribute, which will result in inline
SQL the way any :class:`.ClauseElement` class does.  This covers other
mapped attributes not otherwise transformed by further expression
constructs.

As part of this, it was considered that we could add
__clause_element__() to ClauseElement, however this causes endless loops
in a "while" pattern and this pattern has been identified in third
party libraries.  Add a test to ensure we never make that change.

Change-Id: I9e15b3f1c4883fd3909acbf7dc81d034c6e3ce1d
Fixes: #3802





ORM attributes can now be assigned any object that is has a
``__clause_element__()`` attribute, which will result in inline
SQL the way any :class:`.ClauseElement` class does.  This covers other
mapped attributes not otherwise transformed by further expression
constructs.

As part of this, it was considered that we could add
__clause_element__() to ClauseElement, however this causes endless loops
in a "while" pattern and this pattern has been identified in third
party libraries.  Add a test to ensure we never make that change.

Change-Id: I9e15b3f1c4883fd3909acbf7dc81d034c6e3ce1d
Fixes: #3802