summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/postgresql
Commit message (Collapse)AuthorAgeFilesLines
* Fix argument to array() in array._bind_param()pr/124Andrew2014-07-241-1/+1
| | | array.__init__() expects a list as its sole parameter but inside _bind_param(), instead of sending a list it's sending each item in the list as a separate argument which is incorrect.
* - Fixed bug introduced in 0.9.5 by new pg8000 isolation level featureMike Bayer2014-07-211-2/+6
| | | | | where engine-level isolation level parameter would raise an error on connect. fixes #3134
* - apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,Brian Jarrett2014-07-208-350/+434
| | | | sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
* - Fixed bug in :class:`.Enum` and other :class:`.SchemaType`Mike Bayer2014-07-131-2/+1
| | | | | | | subclasses where direct association of the type with a :class:`.MetaData` would lead to a hang when events (like create events) were emitted on the :class:`.MetaData`. fixes #3124
* - break up the <authors> copyright comment as part of a passMike Bayer2014-07-099-9/+18
| | | | to get all flake8 passing
* - add postgresql_regconfig argument to PG dialect for match() operator,jonathan vanasco2014-07-081-5/+57
| | | | implements PG's to_tsquery('regconfig', 'arg') pattern. fixes #3078
* Merge pull request #101 from ddimmich/mastermike bayer2014-07-073-3/+126
|\ | | | | Postgres 9.4 Jsonb support
| * jsonb support for <@, ?| and ?& added.pr/101Damian Dimmich2014-07-011-1/+18
| | | | | | | | need to see if equality already works.
| * minor cleanup of the jsonb - had extraneous operators that where copiedDamian Dimmich2014-06-281-5/+1
| | | | | | | | | | | | from hstore that don't apply. Add tests for ? and @> operators.
| * add has_key & contains operators for jsonb (ported over from hstore)Damian Dimmich2014-06-281-21/+17
| |
| * initial support for JSONB - this only allows you to define the JSONBDamian Dimmich2014-06-243-3/+117
| | | | | | | | | | datatype - this does not add any of the additional support for querying/indexing yet.
* | - clarify that the pg8000 backend has no impact of any kind onMike Bayer2014-07-041-8/+9
|/ | | | the pg8000 DBAPI's encoding behavior, fixes #3112.
* - Added a new type :class:`.postgresql.OID` to the Postgresql dialect.Mike Bayer2014-06-202-2/+15
| | | | | | | | While "oid" is generally a private type within PG that is not exposed in modern versions, there are some PG use cases such as large object support where these types might be exposed, as well as within some user-reported schema reflection use cases. fixes #3002
* - changelog + docs for pg8000 transaction isolation levelMike Bayer2014-05-303-2/+39
|
* Merge branch 'master' of https://github.com/tlocke/sqlalchemy into tlocke-masterMike Bayer2014-05-301-21/+40
|\
| * PEP 8 tidy of pg8000 dialect and postgresql/test_dialect.pypr/88Tony Locke2014-05-221-14/+11
| |
| * Autocommit isolation level for postgresql+pg8000Tony Locke2014-05-221-0/+24
| | | | | | | | | | | | | | | | As with postgresql+psycopg2, execution_options(isolation_level='AUTOCOMMIT') now works for the postgresql+pg8000 dialect. Also enabled the autocommit test in test_dialect.py for pg8000.
| * Updated doc string for postgresql+pg8000 dialectTony Locke2014-05-211-10/+8
| |
| * pg8000.dbapi is now just pg8000Tony Locke2014-05-211-1/+1
| |
* | update commentsMike Bayer2014-05-301-4/+6
| |
* | Merge branch 'psycopg_disconnect' of https://github.com/dirkmueller/sqlalchemyMike Bayer2014-05-301-1/+5
|\ \
| * | Another Variant for detecting if a connection is closedpr/87Dirk Mueller2014-05-111-1/+5
| | | | | | | | | | | | | | | | | | | | | If there is a closed attribute on the connection and it is true, return true. Implements a todo in the code and helps in one specific disconnect case where it previously did not match because the error message was "unknown error".
* | | - Added the ``hashable=False`` flag to the PG :class:`.HSTORE` type, whichMike Bayer2014-05-251-0/+1
| | | | | | | | | | | | | | | | | | is needed to allow the ORM to skip over trying to "hash" an ORM-mapped HSTORE column when requesting it in a mixed column/entity list. Patch courtesy Gunnlaugur Þór Briem. Fixes #3053
* | | Merge branch 'issue_3034' of ↵Mike Bayer2014-05-161-5/+5
|\ \ \ | |_|/ |/| | | | | https://bitbucket.org/dobesv/sqlalchemy/branch/issue_3034 into ticket_3034
| * | Remove unused importDobes Vandermeer2014-04-251-1/+0
| | |
| * | Use _offset_clause and _limit_clause, which are always Visitable and usually ↵Dobes Vandermeer2014-04-251-5/+5
| | | | | | | | | | | | a BindParameter, instead of _offset and _limit in GenerativeSelect.
| * | Proof-of-concept implementation of supporting bindparam for offset and limit ↵Dobes Vandermeer2014-04-241-2/+3
| | | | | | | | | | | | on a query.
* | | - changelog for #2785Mike Bayer2014-05-161-3/+6
| | | | | | | | | | | | | | | - refactor tests a bit fixes #2785
* | | Merge branch 'zero_indexes-param-for-postgresql-ARRAY-type' of ↵Mike Bayer2014-05-161-1/+16
|\ \ \ | | | | | | | | | | | | https://bitbucket.org/LevonXXL/sqlalchemy/overview into t
| * | | zero_indexes-param-for-postgresql-ARRAY-typeAlexey Terentev2014-05-131-1/+16
| | | |
* | | | Merged in mineo/sqlalchemy/mineo/posgtresql-postgresql-1399232068499 (pull ↵Mike Bayer2014-05-121-1/+1
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | request #17) Posgtresql -> PostgreSQL
| * | | Posgtresql -> PostgreSQLWieland Hoffmann2014-05-041-1/+1
| | |/ | |/|
* | | 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.
* | Fix many typos throughout the codebasepr/85Alex Gaynor2014-04-262-3/+3
|/ | | | Found using: https://github.com/intgr/topy
* added an SSL related connection errorantti_haapala2014-04-111-1/+3
|
* - Fixed ORM bug where changing the primary key of an object, then markingMike Bayer2014-03-281-1/+4
| | | | | | | | | | | | | it for DELETE would fail to target the correct row for DELETE. Then to compound matters, basic "number of rows matched" checks were not being performed. Both issues are fixed, however note that the "rows matched" check requires so-called "sane multi-row count" functionality; the DBAPI's executemany() method must count up the rows matched by individual statements and SQLAlchemy's dialect must mark this feature as supported, currently applies to some mysql dialects, psycopg2, sqlite only. fixes #3006 - Enabled "sane multi-row count" checking for the psycopg2 DBAPI, as this seems to be supported as of psycopg2 2.0.9.
* - Fixed regression caused by release 0.8.5 / 0.9.3's compatibilityMike Bayer2014-03-251-1/+4
| | | | | | | | | enhancements where index reflection on Postgresql versions specific to only the 8.1, 8.2 series again broke, surrounding the ever problematic int2vector type. While int2vector supports array operations as of 8.1, apparently it only supports CAST to a varchar as of 8.3. fix #3000
* - Added an additional message to psycopg2 disconnect detection,Mike Bayer2014-02-191-0/+1
| | | | | | "could not send data to server", which complements the existing "could not receive data from server" and has been observed by users, fixes #2936
* - Support has been improved for Postgresql reflection behavior on very oldMike Bayer2014-02-181-22/+27
| | | | | | | | | | | | (pre 8.1) versions of Postgresql, and potentially other PG engines such as Redshift (assuming Redshift reports the version as < 8.1). The query for "indexes" as well as "primary keys" relies upon inspecting a so-called "int2vector" datatype, which refuses to coerce to an array prior to 8.1 causing failures regarding the "ANY()" operator used in the query. Extensive googling has located the very hacky, but recommended-by-PG-core-developer query to use when PG version < 8.1 is in use, so index and primary key constraint reflection now work on these versions.
* Merge pull request #64 from LevonXXL/mastermike bayer2014-02-161-0/+4
|\ | | | | python_type for ARRAY (PGArray)
| * python_type for ARRAY (PGArray)pr/64Terentev2014-02-031-0/+4
| |
* | - add documentation regarding native hstore flag, psycopg2Mike Bayer2014-02-161-4/+31
| | | | | | | | hstore extension. #2959
* | - Added server version detection to the newly added dialect startupMike Bayer2014-02-141-1/+2
| | | | | | | | | | | | query for "show standard_conforming_strings"; as this variable was added as of PG 8.2, we skip the query for PG versions older than that as well as for backends like Redshift. #2946
* | - Revised this very old issue where the Postgresql "get primary key"Mike Bayer2014-02-141-1/+15
|/ | | | | | | reflection query were updated to take into account primary key constraints that were renamed; the newer query fails on very old versions of Postgresql such as version 7, so the old query is restored in those cases when server_version_info < (8, 0) is detected. #2291
* - Added :paramref:`.MetaData.reflect.**dialect_kwargs`Mike Bayer2014-02-021-38/+149
| | | | | | | | | | | | | | | | | | to support dialect-level reflection options for all :class:`.Table` objects reflected. - Added a new dialect-level argument ``postgresql_ignore_search_path``; this argument is accepted by both the :class:`.Table` constructor as well as by the :meth:`.MetaData.reflect` method. When in use against Postgresql, a foreign-key referenced table which specifies a remote schema name will retain that schema name even if the name is present in the ``search_path``; the default behavior since 0.7.3 has been that schemas present in ``search_path`` would not be copied to reflected :class:`.ForeignKey` objects. The documentation has been updated to describe in detail the behavior of the ``pg_get_constraintdef()`` function and how the ``postgresql_ignore_search_path`` feature essentially determines if we will honor the schema qualification reported by this function or not. [ticket:2922]
* - implement kwarg validation and type system for dialect-specificMike Bayer2014-01-181-7/+12
| | | | | arguments; [ticket:2866] - add dialect specific kwarg functionality to ForeignKeyConstraint, ForeignKey
* - happy new yearMike Bayer2014-01-0510-12/+12
|
* - rework the JSON expression system so that "astext" is called *after*Mike Bayer2013-12-272-33/+91
| | | | | | | | | the indexing. this is for more natural operation. - also add cast() to the JSON expression to complement astext. This integrates the CAST call which will be needed frequently. Part of [ticket:2687]. - it's a little unclear how more advanced unicode attribute-access is going to go, some quick attempts at testing yielded strange error messages from psycopg2. - do other cross linking as mentioned in [ticket:2687].
* - make the json serializer and deserializer per-dialect, so that we areMike Bayer2013-12-173-15/+28
| | | | | compatible with psycopg2's per-connection/cursor approach. add round trip tests for both native and non-native.
* - rework JSON expressions to be based off __getitem__ exclusivelyMike Bayer2013-12-173-38/+44
| | | | | | | | | - add support for "standalone" JSON objects; this involves getting CAST to upgrade the given type of a bound parameter. should add a core-only test for this. - add tests for "standalone" json round trips both with and without unicode - add mechanism by which we remove psycopg2's "json" handler in order to get the effect of using our non-native result handlers
View Lorry Controller Status