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

	Commit message (Collapse)	Author	Age	Files	Lines
*	- apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,	Brian Jarrett	2014-07-20	1	-53/+56
\| \| \| \|	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
*	Fix many typos throughout the codebasepr/85	Alex Gaynor	2014-04-26	1	-2/+2
\| \| \| \|	Found using: https://github.com/intgr/topy
*	- happy new year	Mike Bayer	2014-01-05	1	-1/+1
\|
*	Fix indentation issues in docstringspr/43	Vraj Mohan	2013-11-12	1	-1/+1
\|
*	Replace a big loop + dict lookup in Connection.execute() with a simple visitorpr/30	Alex Gaynor	2013-09-25	1	-0/+3
\| \| \| \|	pattern
*	more seealsos...	Mike Bayer	2013-08-27	1	-3/+4
\|
*	added "system=True" to Column, so that we generally don't have to bother	Mike Bayer	2013-08-25	1	-5/+10
\| \| \| \|	with CreateColumn rules
*	- The :class:`.CreateColumn` construct can be appled to a custom	Mike Bayer	2013-08-24	1	-0/+29
\| \| \| \| \|	compilation rule which allows skipping of columns, by producing a rule that returns ``None``. Also in 0.8.3.
*	- header comments	Mike Bayer	2013-08-12	1	-1/+1
\|
*	- A large refactoring of the ``sqlalchemy.sql`` package has reorganized	Mike Bayer	2013-08-12	1	-0/+826
	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.