delta/python-packages/sqlalchemy.git/lib/sqlalchemy/dialects/sqlite, branch pr/33

move FAQ to the docs, [ticket:2133]

2013-08-21T22:48:34+00:00

doc fix

2013-07-13T02:01:58+00:00

The newly added SQLite DATETIME arguments storage_format and

2013-07-13T01:52:54+00:00

regexp apparently were not fully implemented correctly; while the
arguments were accepted, in practice they would have no effect;
this has been fixed.  Also in 0.8.3.
[ticket:2781]

Added :class:`.BIGINT` to the list of type names that can be

2013-07-02T22:10:08+00:00

reflected by the SQLite dialect; courtesy Russell Stuart.
[ticket:2764]

Fix unique constraints reflection in SQLite

2013-06-23T07:42:03+00:00

If SQLite keywords are used as column names, they are
quoted. The code parsing the information about table
unique constraints should be modified so that it properly
removes double-quotes from column names.

Add basic support of unique constraints reflection

2013-06-09T20:49:55+00:00

Inspection API already supports reflection of table
indexes information and those also include unique
constraints (at least for PostgreSQL and MySQL).
But it could be actually useful to distinguish between
indexes and plain unique constraints (though both are
implemented in the same way internally in RDBMS).

This change adds a new method to Inspection API - get_unique_constraints()
and implements it for SQLite, PostgreSQL and MySQL dialects.

working through tests....

2013-06-03T00:23:03+00:00

- add a test specific to sqlite testing cursor.description encoding (should

2013-05-26T20:58:37+00:00

probably be one in test_query or test_unicode...)
- fix up test_unitofwork

sqlite tests

2013-05-26T17:10:00+00:00

- unicode literals need to just be handled differently if they have utf-8

2013-05-04T18:59:26+00:00

encoded in them vs. unicode escaping.  not worth figuring out how to combine
these right now