[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.