summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/ext/compiler.py
Commit message (Collapse)AuthorAgeFilesLines
* Support python3.6Mike Bayer2017-01-131-3/+3
| | | | | | | | | | | Corrects some warnings and adds tox config. Adds DeprecationWarning to the error category. Large sweep for string literals w/ backslashes as this is common in docstrings Co-authored-by: Andrii Soldatenko Fixes: #3886 Change-Id: Ia7c838dfbbe70b262622ed0803d581edc736e085 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/337
* update for 2017 copyrightMike Bayer2017-01-041-1/+1
| | | | Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de
* spelling: Postgresql -> PostgreSQLVille Skyttä2016-10-081-1/+1
|
* Ensure @compiles calls down to the original compilation schemeMike Bayer2016-06-291-2/+15
| | | | | | | | | | | | | | | Made a slight behavioral change in the ``sqlalchemy.ext.compiler`` extension, whereby the existing compilation schemes for an established construct would be removed if that construct was itself didn't already have its own dedicated ``__visit_name__``. This was a rare occurrence in 1.0, however in 1.1 :class:`.postgresql.ARRAY` subclasses :class:`.sqltypes.ARRAY` and has this behavior. As a result, setting up a compilation handler for another dialect such as SQLite would render the main :class:`.postgresql.ARRAY` object no longer compilable. Fixes: #3732 Change-Id: If2c1ada4eeb09157885888e41f529173902f2b49
* - happy new yearMike Bayer2016-01-291-1/+1
|
* - add a note that the literal_binds flag should be usedMike Bayer2016-01-201-1/+11
| | | | when cross-compiling from DDL to SQL, fixes #3615
* - copyright 2015Mike Bayer2015-03-101-1/+1
|
* PEP8 style fixesBrian Jarrett2014-07-131-5/+7
|
* - break up the <authors> copyright comment as part of a passMike Bayer2014-07-091-1/+2
| | | | to get all flake8 passing
* Documentation fix-up: "its" vs. "it's"pr/91Matthias Urlichs2014-05-111-1/+1
| | | | | | | | | Removed ungrammatical apostrophes from documentation, replacing "it's" with "its" where appropriate (but in a few cases with "it is" when that read better). While doing that, I also fixed a couple of minor typos etc. as I noticed them.
* - happy new yearMike Bayer2014-01-051-1/+1
|
* Fix cross referencesVraj Mohan2013-11-121-1/+1
|
* - Added new method to the :func:`.insert` constructMike Bayer2013-07-051-0/+6
| | | | | | | | | | :meth:`.Insert.from_select`. Given a list of columns and a selectable, renders ``INSERT INTO (table) (columns) SELECT ..``. While this feature is highlighted as part of 0.9 it is also backported to 0.8.3. [ticket:722] - The :func:`.update`, :func:`.insert`, and :func:`.delete` constructs will now interpret ORM entities as FROM clauses to be operated upon, in the same way that select() already does. Also in 0.8.3.
* happy new year (see #2645)Diana Clarke2013-01-011-1/+1
|
* fixing broken links (see #2625)Diana Clarke2012-12-061-5/+6
|
* just a pep8 pass of lib/sqlalchemy/extDiana Clarke2012-11-191-47/+63
|
* - [feature] Added a hook to the system of renderingMike Bayer2012-09-091-0/+15
| | | | | | | CREATE TABLE that provides access to the render for each Column individually, by constructing a @compiles function against the new schema.CreateColumn construct. [ticket:2463]
* - move ext to relative importsMike Bayer2012-07-171-25/+25
|
* happy new yearMike Bayer2012-01-041-1/+1
|
* - [bug] the @compiles decorator raises anMike Bayer2011-12-061-1/+7
| | | | | | informative error message when no "default" compilation handler is present, rather than KeyError.
* document autocommit when using the compiler extension, update the ↵Mike Bayer2011-08-181-0/+49
| | | | "understanding autocommit" section
* - add some function examples, [ticket:2107]Mike Bayer2011-04-021-1/+117
| | | | | | - have "packagenames" be present on FunctionElement by default so that compiler.visit_function() can be called - add a test for that
* - whitespace removal bonanzaMike Bayer2011-01-021-17/+17
|
* - clean up copyright, update for 2011, stamp every file withMike Bayer2011-01-021-0/+6
| | | | | a consistent tag - AUTHORS file
* almost through.Mike Bayer2010-09-041-0/+2
|
* - 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.