summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/postgresql
Commit message (Collapse)AuthorAgeFilesLines
* sqlalchemy/dialects/postgresql/pgjson:pr/50nathan2013-12-111-7/+14
| | | | - Updated documentation for JSON class
* sqlalchemy/dialects/postgresql/pgjson:nathan2013-12-111-2/+14
| | | | | - Added support for additional operators - Made return as json default (rather than text)
* sqlalchemy/dialects/postgresql/psycopg2:nathan2013-12-101-2/+0
| | | | - Removed unneeded import of psycopg2.extensions
* sqlalchemy/dialects/postgresql/pgjson:nathan2013-12-102-2/+19
| | | | | | | | | | | | - Fixed reference to HSTORE - Corrected spelling of SQLAlchemy sqlalchemy/dialects/postgresql/psycopg2: - Added psycopg2 specific wrapper type for JSON which uses inherent json deserialization facilities - Added code to detect and utilize the JSON wrapper if psycopg2 >= 2.5 test/dialect/postgresql/test_types: - removed reference to use_native_hstore
* sqlalchemy/dialects/postgresql/__init__.py:nathan2013-12-093-1/+114
| | | | | | | | | | - Added import references to JSON class sqlalchemy/dialects/postgresql/base.py: - Added visitor method for JSON class sqlalchemy/dialects/postgresql/pgjson (new): - JSON class, supports automatic serialization and deserialization of json data, as well as basic json operators.
* - Fixed bug where values within an ENUM weren't escaped for singleMike Bayer2013-11-301-1/+3
| | | | | quote signs. Note that this is backwards-incompatible for existing workarounds that manually escape the single quotes. [ticket:2878]
* - add support for bindparam() called from AsFromTextMike Bayer2013-11-291-13/+16
| | | | | - get PG dialect to work around "no nonexistent binds" rule for now, though we might want to reconsider this behavior
* - add support for specifying tables or entities for "of"Mike Bayer2013-11-281-2/+3
| | | | | - implement Query with_for_update() - rework docs and tests
* - fix up rendering of "of"Mike Bayer2013-11-281-4/+4
| | | | | | - move out tests, dialect specific out of compiler, compiler tests use new API, legacy API tests in test_selecatble - add support for adaptation of ForUpdateArg, alias support in compilers
* - work in progress, will squashMike Bayer2013-11-281-28/+16
|
* Merge branch 'for_update_of' of github.com:mlassnig/sqlalchemy into ↵Mike Bayer2013-11-281-7/+29
|\ | | | | | | for_update_of
| * added LockmodeArgspr/42Mario Lassnig2013-11-281-9/+21
| |
| * added ORM supportMario Lassnig2013-11-141-8/+16
| |
| * add psql FOR UPDATE OF functionalityMario Lassnig2013-11-121-0/+2
| |
* | pg8000 fix for decimal return scaleMike Bayer2013-11-231-1/+2
| |
* | - evaulate decimal_return_scale statelessly. Don't re-assign to ↵Mike Bayer2013-11-231-1/+2
| | | | | | | | | | | | self.decimal_return_scale so that __repr__() is maintained (for alembic tests)
* | - The precision used when coercing a returned floating point value toMike Bayer2013-11-222-2/+4
|/ | | | | | | | | | Python ``Decimal`` via string is now configurable. The flag ``decimal_return_scale`` is now supported by all :class:`.Numeric` and :class:`.Float` types, which will ensure this many digits are taken from the native floating point value when it is converted to string. If not present, the type will make use of the value of ``.scale``, if the type supports this setting and it is non-None. Otherwise the original default length of 10 is used. [ticket:2867]
* - Fixed bug where index reflection would mis-interpret indkey valuesMike Bayer2013-10-271-1/+4
| | | | | | when using the pypostgresql adapter, which returns these values as lists vs. psycopg2's return type of string. [ticket:2855]
* Merge branch 'master' of github.com:ijl/sqlalchemy into merge_2183Mike Bayer2013-10-251-5/+24
|\
| * PostgreSQL foreign key inspection includes optionsijl2013-10-111-5/+24
| |
* | - The typing system now handles the task of rendering "literal bind" values,Mike Bayer2013-10-201-9/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | e.g. values that are normally bound parameters but due to context must be rendered as strings, typically within DDL constructs such as CHECK constraints and indexes (note that "literal bind" values become used by DDL as of :ticket:`2742`). A new method :meth:`.TypeEngine.literal_processor` serves as the base, and :meth:`.TypeDecorator.process_literal_param` is added to allow wrapping of a native literal rendering method. [ticket:2838] - enhance _get_colparams so that we can send flags like literal_binds into INSERT statements - add support in PG for inspecting standard_conforming_strings - add a new series of roundtrip tests based on INSERT of literal plus SELECT for basic literal rendering in dialect suite
* | - attempt to clarify what mutable extension does for HSTORE, [ticket:2803]Mike Bayer2013-10-181-2/+9
| |
* | - Removed a 128-character truncation from the reflection of theMike Bayer2013-10-181-2/+1
| | | | | | | | | | | | server default for a column; this code was original from PG system views which truncated the string for readability. [ticket:2844]
* | - Added support for rendering ``SMALLSERIAL`` when a :class:`.SmallInteger`Mike Bayer2013-10-151-1/+11
| | | | | | | | | | | | type is used on a primary key autoincrement column, based on server version detection of Postgresql version 9.2 or greater. [ticket:2840]
* | Parenthesis will be applied to a compound SQL expression asMike Bayer2013-10-121-1/+4
| | | | | | | | | | rendered in the column list of a CREATE INDEX statement. [ticket:2742]
* | - Fixed bug in default compiler plus those of postgresql, mysql, andMike Bayer2013-10-121-9/+8
|/ | | | | | | | mssql to ensure that any literal SQL expression values are rendered directly as literals, instead of as bound parameters, within a CREATE INDEX statement. [ticket:2742] - don't need expression_as_ddl(); literal_binds and include_table take care of this functionality.
* - put exact version string in the testMike Bayer2013-09-291-2/+2
| | | | - use match with a .* preceding instead of search
* re.match to re.searchpr/26Scott Schaefer2013-09-061-1/+1
| | | | | Convert to re.search to eliminate the restriction on only matching the beginning of the string
* - A rework to the way that "quoted" identifiers are handled, in thatMike Bayer2013-08-271-4/+4
| | | | | | | | | | | | | | | | instead of relying upon various ``quote=True`` flags being passed around, these flags are converted into rich string objects with quoting information included at the point at which they are passed to common schema constructs like :class:`.Table`, :class:`.Column`, etc. This solves the issue of various methods that don't correctly honor the "quote" flag such as :meth:`.Engine.has_table` and related methods. The :class:`.quoted_name` object is a string subclass that can also be used explicitly if needed; the object will hold onto the quoting preferences passed and will also bypass the "name normalization" performed by dialects that standardize on uppercase symbols, such as Oracle, Firebird and DB2. The upshot is that the "uppercase" backends can now work with force-quoted names, such as lowercase-quoted names and new reserved words. [ticket:2812]
* The behavior of :func:`.extract` has been simplified on theMike Bayer2013-06-281-22/+0
| | | | | | | | | Postgresql dialect to no longer inject a hardcoded ``::timestamp`` or similar cast into the given expression, as this interfered with types such as timezone-aware datetimes, but also does not appear to be at all necessary with modern versions of psycopg2. Also in 0.8.2. [ticket:2740]
* Fixed bug in HSTORE type where keys/values that containedMike Bayer2013-06-281-3/+3
| | | | | | | backslashed quotes would not be escaped correctly when using the "non native" (i.e. non-psycopg2) means of translating HSTORE data. Patch courtesy Ryan Kelly. [ticket:2766]
* Fix indexes reflection in PostgreSQLpr/13Roman Podolyaka2013-06-261-14/+18
| | | | | | Reflection of indexes must preserve the order of columns. Fixes issue 2767.
* Fix unique constraints reflection in PostgreSQLpr/11Roman Podolyaka2013-06-231-9/+16
| | | | Reflection of unique constraints must preserve the order of columns.
* versionaddsMike Bayer2013-06-221-6/+33
|
* - 0.8 changelogMike Bayer2013-06-221-11/+11
| | | | - some whitespace
* Merge pull request #5 from cjw296/pg-rangesmike bayer2013-06-224-2/+246
|\ | | | | Support for Postgres range types.
| * Documentation for the new range type support.pr/5Chris Withers2013-06-103-6/+19
| |
| * Implement EXCLUDE constraints for postgres.Chris Withers2013-06-103-0/+90
| |
| * add support for range operators listed in ↵Chris Withers2013-06-101-6/+75
| | | | | | | | http://www.postgresql.org/docs/9.2/interactive/functions-range.html
| * Basic type support for the new range types in postgres 9.2Chris Withers2013-06-103-1/+73
| |
* | fix up the isolation level docs which were a messMike Bayer2013-06-172-25/+58
| |
* | - changelogMike Bayer2013-06-152-3/+8
| | | | | | | | - docs
* | Add AUTOCOMMIT isolation level support for psycopg2pr/7Roman Podolyaka2013-06-151-0/+1
|/ | | | | | | | | | | | | | One can use this to emit statements, which can not be executed within a transaction (e. g. CREATE DATABASE): from sqlalchemy import create_engine eng = create_engine('postgresql://test:test@localhost/test') conn = eng.connect().execution_options(isolation_level='AUTOCOMMIT') conn.execute('CREATE DATABASE test2;') Fixes issue #2072.
* Add basic support of unique constraints reflectionpr/4Roman Podolyaka2013-06-091-0/+30
| | | | | | | | | | | | Inspection API already supports reflection of table indexes information and those also include unique constraints (at least for PostgreSQL and MySQL). But it could be actually useful to distinguish between indexes and plain unique constraints (though both are implemented in the same way internally in RDBMS). This change adds a new method to Inspection API - get_unique_constraints() and implements it for SQLite, PostgreSQL and MySQL dialects.
* Merge branch 'rel_0_9'Mike Bayer2013-05-293-46/+43
|\ | | | | | | | | | | | | Conflicts: lib/sqlalchemy/dialects/postgresql/hstore.py lib/sqlalchemy/util/__init__.py lib/sqlalchemy/util/compat.py
| * - repair for py3kMike Bayer2013-05-291-1/+6
| | | | | | | | - fix test
| * Unicode support for psycopg2 native hstore implementationDmitry Mugtasimov2013-05-291-1/+2
| |
| * hstores are text, and in py3k they seem to be implcitly unicode. soMike Bayer2013-05-291-10/+26
| | | | | | | | | | add unicode encoding for py2k for the non-native hstore, pullreq for native psycopg2 support coming....
| * postgresql testsMike Bayer2013-05-262-21/+19
| |
| * postgresql dialect testsMike Bayer2013-04-282-27/+25
| |
View Lorry Controller Status