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

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

8 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4eb5d44cecb5/
Changeset:   4eb5d44cecb5
Branch:      None
User:        eblume
Date:        2014-01-31 01:37:18
Summary:     Don't include .egg files in the repo

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/c188526a7448/
Changeset:   c188526a7448
Branch:      None
User:        eblume
Date:        2014-01-31 04:13:18
Summary:     PEP-8 compliance for dialects/sqlite/base.py

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/e47f99450378/
Changeset:   e47f99450378
Branch:      None
User:        eblume
Date:        2014-02-04 01:55:00
Summary:     SQLite dialect - support relection from affinity

SQLite allows column types that aren't technically understood in sqlite
by using 'data affinity', which is an algorithm for converting column
types in to some sort of useful type that can be stored and retrieved
from the db. Unfortunatly, this breaks reflection since we (previously)
expected a sqlite db to reflect column types that we permit in the
`ischema_names` for that dialect.

This patch changes the logic for 'unknown' column types during
reflection to instead run through SQLite's data affinity algorithm, and
assigns appropriate types from that.

It also expands the matching for column type to include column types
with spaces (strongly discouraged but allowed by sqlite) and also
completely empty column types (in which case the NullType is assigned,
which sqlite will treat as a Blob - or rather, Blob is treated as
NullType). These changes mean that SQLite will never raise an error for
an unknown type during reflection - there will always be some 'useful'
type returned, which follows the spirit of SQLite (accomodation before
sanity!).

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/198a900bd19d/
Changeset:   198a900bd19d
Branch:      None
User:        zzzeek
Date:        2014-02-16 22:43:42
Summary:     Merge branch 'master' of https://github.com/eblume/sqlalchemy into t

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/79f801eae889/
Changeset:   79f801eae889
Branch:      None
User:        zzzeek
Date:        2014-02-16 23:10:05
Summary:     - changelog + documentation for pullreq github:65

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/5e100a70c513/
Changeset:   5e100a70c513
Branch:      None
User:        zzzeek
Date:        2014-02-16 23:20:18
Summary:     - The SQLite dialect will now skip unsupported arguments when reflecting
types; such as if it encounters a string like ``INTEGER(5)``, the
:class:`.INTEGER` type will be instantiated without the "5" being included,
based on detecting a ``TypeError`` on the first attempt.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/5bc3b7fe6b88/
Changeset:   5bc3b7fe6b88
Branch:      None
User:        zzzeek
Date:        2014-02-16 23:20:35
Summary:     - need qualifiers here...

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/00c6ebb44089/
Changeset:   00c6ebb44089
Branch:      None
User:        zzzeek
Date:        2014-02-17 00:14:10
Summary:     - rewrite SQLite reflection tests into one consistent fixture, which tests
both _resolve_type_affinity() directly as well as round trip tests fully.

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.