| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | - A large refactoring of the ``sqlalchemy.sql`` package has reorganized | Mike Bayer | 2013-08-12 | 1 | -176/+0 |
| | | | | | | | | | | | | | | | | | | | | | | | the import structure of many core modules. ``sqlalchemy.schema`` and ``sqlalchemy.types`` remain in the top-level package, but are now just lists of names that pull from within ``sqlalchemy.sql``. Their implementations are now broken out among ``sqlalchemy.sql.type_api``, ``sqlalchemy.sql.sqltypes``, ``sqlalchemy.sql.schema`` and ``sqlalchemy.sql.ddl``, the last of which was moved from ``sqlalchemy.engine``. ``sqlalchemy.sql.expression`` is also a namespace now which pulls implementations mostly from ``sqlalchemy.sql.elements``, ``sqlalchemy.sql.selectable``, and ``sqlalchemy.sql.dml``. Most of the "factory" functions used to create SQL expression objects have been moved to classmethods or constructors, which are exposed in ``sqlalchemy.sql.expression`` using a programmatic system. Care has been taken such that all the original import namespaces remain intact and there should be no impact on any existing applications. The rationale here was to break out these very large modules into smaller ones, provide more manageable lists of function names, to greatly reduce "import cycles" and clarify the up-front importing of names, and to remove the need for redundant functions and documentation throughout the expression package. | ||||
| * | - replace most explicitly-named test objects called "Mock..." with | Mike Bayer | 2013-06-30 | 1 | -19/+11 |
| | | | | | | | | | | | | | actual mock objects from the mock library. I'd like to use mock for new tests so we might as well use it in obvious places. - use unittest.mock in py3.3 - changelog - add a note to README.unittests - add tests_require in setup.py - have tests import from sqlalchemy.testing.mock - apply usage of mock to one of the event tests. we can be using this approach all over the place. | ||||
| * | - the raw 2to3 run | Mike Bayer | 2013-04-27 | 1 | -1/+1 |
| | | | | | - went through examples/ and cleaned out excess list() calls | ||||
| * | - :meth:`.MetaData.create_all` and :meth:`.MetaData.drop_all` will | Mike Bayer | 2013-03-02 | 1 | -0/+184 |
| now accommodate an empty list as an instruction to not create/drop any items, rather than ignoring the collection. [ticket:2664]. This is a behavioral change and extra notes to the changelog and migration document have been added. - create a new test suite for exercising codepaths in engine/ddl.py | |||||
 |
index : delta/python-packages/sqlalchemy.git | |
| github.com: zzzeek/sqlalchemy.git |
| summaryrefslogtreecommitdiff |