delta/python-packages/sqlalchemy.git - github.com: zzzeek/sqlalchemy.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	- happy new year	Mike Bayer	2016-01-29	1	-1/+1
\|
*	- copyright 2015	Mike Bayer	2015-03-10	1	-1/+1
\|
*	- this is small optimization, currently it's the best we can do	Mike Bayer	2014-08-28	1	-1/+2
\| \| \| \|	for #3175. fixes #3175 (for now)
*	- apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,	Brian Jarrett	2014-07-20	1	-8/+11
\| \| \| \|	sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
*	- break up the <authors> copyright comment as part of a pass	Mike Bayer	2014-07-09	1	-1/+2
\| \| \| \|	to get all flake8 passing
*	- Fixed an 0.9 regression where the automatic aliasing applied by	Mike Bayer	2014-01-23	1	-2/+11
\| \| \| \| \| \| \| \| \| \|	:class:`.Query` and in other situations where selects or joins were aliased (such as joined table inheritance) could fail if a user-defined :class:`.Column` subclass were used in the expression. In this case, the subclass would fail to propagate ORM-specific "annotations" along needed by the adaptation. The "expression annotations" system has been corrected to account for this case. [ticket:2918]
*	- happy new year	Mike Bayer	2014-01-05	1	-1/+1
\|
*	- A large refactoring of the ``sqlalchemy.sql`` package has reorganized	Mike Bayer	2013-08-12	1	-0/+182
	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.