summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/ext/compiler.py
Commit message (Collapse)AuthorAgeFilesLines
...
* - The 'default' compiler is automatically copied overMike Bayer2010-07-021-1/+6
| | | | | | | | when overriding the compilation of a built in clause construct, so no KeyError is raised if the user-defined compiler is specific to certain backends and compilation for a different backend is invoked. [ticket:1838]
* add example for changing TypeEngine compilationMike Bayer2010-04-071-1/+18
|
* add FunctionElement exampleMike Bayer2010-04-021-2/+17
|
* - the compiler extension now allows @compiles decoratorsMike Bayer2010-03-301-1/+1
| | | | | | on base classes that extend to child classes, @compiles decorators on child classes that aren't broken by a @compiles decorator on the base class.
* - Made sqlalchemy.sql.expressions.Executable part of publicMike Bayer2010-02-121-1/+8
| | | | | | | | | | | API, used for any expression construct that can be sent to execute(). FunctionElement now inherits Executable so that it gains execution_options(), which are also propagated to the select() that's generated within execute(). Executable in turn subclasses _Generative which marks any ClauseElement that supports the @_generative decorator - these may also become "public" for the benefit of the compiler extension at some point.
* add a note about type for ColumnElementMike Bayer2010-02-071-0/+8
|
* some compile docsMike Bayer2009-12-301-2/+40
|
* - subclassed Function off of new FunctionElement generic baseMike Bayer2009-11-101-11/+42
| | | | | | - removed "key" accessor of Function, Grouping - this doesn't seem to be used for anything - various formatting - documented the four "Element" classes in the compiler extension as per [ticket:1590]
* merge 0.6 series to trunk.Mike Bayer2009-08-061-4/+4
|
* - Back-ported the "compiler" extension from SQLA 0.6. Thisrel_0_5_4Mike Bayer2009-05-171-0/+110
is a standardized interface which allows the creation of custom ClauseElement subclasses and compilers. In particular it's handy as an alternative to text() when you'd like to build a construct that has database-specific compilations. See the extension docs for details.