summaryrefslogtreecommitdiff
path: root/doc/build/dialects/postgresql.rst
Commit message (Collapse)AuthorAgeFilesLines
* - reorganize docs so expression, schema are broken out into subfiles, ↵Mike Bayer2013-08-181-20/+19
| | | | | | they're too big - fix the targeting of module names moved around by using custom handlers for "Bases", etc.
* Tidy range types docs and add warning about the return type support offered ↵pr/12Chris Withers2013-06-261-2/+18
| | | | by different versions of different DBAPI libraries.
* Fix NameError in example.Chris Withers2013-06-261-4/+1
|
* Documentation for the new range type support.pr/5Chris Withers2013-06-101-1/+50
|
* Add ANY/ALL construct support for PostgreSQL's ARRAY typeAudrius Kažukauskas2013-01-281-3/+7
|
* Add special containment operation methods for PG array typeAudrius Kažukauskas2012-11-201-1/+1
|
* - hstore documentation, migrationMike Bayer2012-11-171-0/+5
| | | | - don't need a custom exception here, just use ValueError
* - add HSTOREMike Bayer2012-11-171-0/+3
| | | | - this was a mistake in mutable
* glossary updatesMike Bayer2012-10-281-2/+0
|
* - rework the sphinx customizations into distinct modulesMike Bayer2012-10-191-7/+0
| | | | | | | - build a new Sphinx extension that allows dialect info to be entered as directives which is then rendered consistently throughout all dialect/dbapi sections - break out the "empty_strings" requirement for oracle test
* - move out maxdbMike Bayer2012-10-181-4/+11
| | | | | | - begin consolidating docs for dialects to be more self contained - add a separate section for "external" dialects - not sure how we're going to go with this yet.
* - [feature] The Core oeprator system now includesMike Bayer2012-08-201-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the `getitem` operator, i.e. the bracket operator in Python. This is used at first to provide index and slice behavior to the Postgresql ARRAY type, and also provides a hook for end-user definition of custom __getitem__ schemes which can be applied at the type level as well as within ORM-level custom operator schemes. Note that this change has the effect that descriptor-based __getitem__ schemes used by the ORM in conjunction with synonym() or other "descriptor-wrapped" schemes will need to start using a custom comparator in order to maintain this behavior. - [feature] postgresql.ARRAY now supports indexing and slicing. The Python [] operator is available on all SQL expressions that are of type ARRAY; integer or simple slices can be passed. The slices can also be used on the assignment side in the SET clause of an UPDATE statement by passing them into Update.values(); see the docs for examples. - [feature] Added new "array literal" construct postgresql.array(). Basically a "tuple" that renders as ARRAY[1,2,3].
* - [feature] Added create_type constructor argumentMike Bayer2011-11-281-1/+1
| | | | | | | | | to pg.ENUM. When False, no CREATE/DROP or checking for the type will be performed as part of a table create/drop event; only the create()/drop)() methods called directly will do this. Helps with Alembic "offline" scripts.
* - Documented SQLite DATE/TIME/DATETIME types.Mike Bayer2011-03-271-0/+2
| | | | | | [ticket:2029] (also in 0.6.7) - add "currentmodule" directive to all the dialect type docs to ensure users import from the dialect package, not the "base" module
* - execution_options() on Connection acceptsMike Bayer2011-01-161-0/+2
| | | | | | | | | | "isolation_level" argument, sets transaction isolation level for that connection only until returned to the connection pool, for thsoe backends which support it (SQLite, Postgresql) [ticket:2001] - disallow the option on Engine (use isolation_level to create_engine()), Executable (we don't want to check/set per statement) - docs
* experiment with removing the API section and putting docstrings inline.Mike Bayer2010-09-041-0/+86
new outline section is provided with a new flow.
View Lorry Controller Status