id dZddlmZddlZddlZddlmZddlm Z ddlm Z ddlm Zd d lmZd d lmZd d lmZd d lmZd dlmZd dlmZd dlmZd dlmZd dlmZd dlmZd d lmZd dlmZd dlmZd dlmZd dlm Z d dlm!Z!d dlm"Z"d dlm#Z#d dlm$Z$d dlm%Z%d dlm&Z&d dlm'Z'd dlm(Z( dd l)m*Z+n #e,$rdZ+YnwxYwej-d!ej.Z/ej-d"ej.ej0zZ1e2gd#Z3d$Z4d%Z5d&Z6Gd'd(ej7Z8Gd)d*ej9Z:Gd+d,ej;Ze>Z?Gd/d0ej;Z@e@ZAGd1d2ej;ZBGd3d4ej;ZCGd5d6ej;ZDGd7d8ejEZEGd9d:ejFZFGd;dej;ZKeKZLGd?d@ej;Z*e*ZMGdAdBej;ZNGdCdDejGejOZPejQejQejReIejOePejSjTe jTejSe jSiZUidEejQdFe jVdGe jSdHe jWdIejXdJejYdKejZdLej[dMej\dNej]dOe#dPedQe&dRe(dSe dTej^dUej^idVe'dWe$dXe"dYe%dZe<d[e>d\e*d]eKd^eKd_e@d`eBdaeCdbeDdce:ddeEdeeEdfeEeFeFe!eFe8eeIeNdgZ_Gdhdiej`ZaGdjdkejbZcGdldmejdZeGdndoejfZgGdpdqejhZiGdrdsejjZkGdtduejjZlGdvdwejmZnGdxdyejoZpdS)za .. dialect:: postgresql :name: PostgreSQL .. _postgresql_sequences: Sequences/SERIAL/IDENTITY ------------------------- PostgreSQL supports sequences, and SQLAlchemy uses these as the default means of creating new primary key values for integer-based primary key columns. When creating tables, SQLAlchemy will issue the ``SERIAL`` datatype for integer-based primary key columns, which generates a sequence and server side default corresponding to the column. To specify a specific named sequence to be used for primary key generation, use the :func:`~sqlalchemy.schema.Sequence` construct:: Table('sometable', metadata, Column('id', Integer, Sequence('some_id_seq'), primary_key=True) ) When SQLAlchemy issues a single INSERT statement, to fulfill the contract of having the "last insert identifier" available, a RETURNING clause is added to the INSERT statement which specifies the primary key columns should be returned after the statement completes. The RETURNING functionality only takes place if PostgreSQL 8.2 or later is in use. As a fallback approach, the sequence, whether specified explicitly or implicitly via ``SERIAL``, is executed independently beforehand, the returned value to be used in the subsequent insert. Note that when an :func:`~sqlalchemy.sql.expression.insert()` construct is executed using "executemany" semantics, the "last inserted identifier" functionality does not apply; no RETURNING clause is emitted nor is the sequence pre-executed in this case. To force the usage of RETURNING by default off, specify the flag ``implicit_returning=False`` to :func:`_sa.create_engine`. PostgreSQL 10 IDENTITY columns ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL 10 has a new IDENTITY feature that supersedes the use of SERIAL. Built-in support for rendering of IDENTITY is not available yet, however the following compilation hook may be used to replace occurrences of SERIAL with IDENTITY:: from sqlalchemy.schema import CreateColumn from sqlalchemy.ext.compiler import compiles @compiles(CreateColumn, 'postgresql') def use_identity(element, compiler, **kw): text = compiler.visit_create_column(element, **kw) text = text.replace("SERIAL", "INT GENERATED BY DEFAULT AS IDENTITY") return text Using the above, a table such as:: t = Table( 't', m, Column('id', Integer, primary_key=True), Column('data', String) ) Will generate on the backing database as:: CREATE TABLE t ( id INT GENERATED BY DEFAULT AS IDENTITY NOT NULL, data VARCHAR, PRIMARY KEY (id) ) .. _postgresql_isolation_level: Transaction Isolation Level --------------------------- Most SQLAlchemy dialects support setting of transaction isolation level using the :paramref:`_sa.create_engine.execution_options` parameter at the :func:`_sa.create_engine` level, and at the :class:`_engine.Connection` level via the :paramref:`.Connection.execution_options.isolation_level` parameter. For PostgreSQL dialects, this feature works either by making use of the DBAPI-specific features, such as psycopg2's isolation level flags which will embed the isolation level setting inline with the ``"BEGIN"`` statement, or for DBAPIs with no direct support by emitting ``SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL `` ahead of the ``"BEGIN"`` statement emitted by the DBAPI. For the special AUTOCOMMIT isolation level, DBAPI-specific techniques are used which is typically an ``.autocommit`` flag on the DBAPI connection object. To set isolation level using :func:`_sa.create_engine`:: engine = create_engine( "postgresql+pg8000://scott:tiger@localhost/test", execution_options={ "isolation_level": "REPEATABLE READ" } ) To set using per-connection execution options:: with engine.connect() as conn: conn = conn.execution_options( isolation_level="REPEATABLE READ" ) with conn.begin(): # ... work with transaction Valid values for ``isolation_level`` on most PostgreSQL dialects include: * ``READ COMMITTED`` * ``READ UNCOMMITTED`` * ``REPEATABLE READ`` * ``SERIALIZABLE`` * ``AUTOCOMMIT`` .. seealso:: :ref:`dbapi_autocommit` :ref:`psycopg2_isolation_level` :ref:`pg8000_isolation_level` .. _postgresql_schema_reflection: Remote-Schema Table Introspection and PostgreSQL search_path ------------------------------------------------------------ **TL;DR;**: keep the ``search_path`` variable set to its default of ``public``, name schemas **other** than ``public`` explicitly within ``Table`` definitions. The PostgreSQL dialect can reflect tables from any schema. The :paramref:`_schema.Table.schema` argument, or alternatively the :paramref:`.MetaData.reflect.schema` argument determines which schema will be searched for the table or tables. The reflected :class:`_schema.Table` objects will in all cases retain this ``.schema`` attribute as was specified. However, with regards to tables which these :class:`_schema.Table` objects refer to via foreign key constraint, a decision must be made as to how the ``.schema`` is represented in those remote tables, in the case where that remote schema name is also a member of the current `PostgreSQL search path `_. By default, the PostgreSQL dialect mimics the behavior encouraged by PostgreSQL's own ``pg_get_constraintdef()`` builtin procedure. This function returns a sample definition for a particular foreign key constraint, omitting the referenced schema name from that definition when the name is also in the PostgreSQL schema search path. The interaction below illustrates this behavior:: test=> CREATE TABLE test_schema.referred(id INTEGER PRIMARY KEY); CREATE TABLE test=> CREATE TABLE referring( test(> id INTEGER PRIMARY KEY, test(> referred_id INTEGER REFERENCES test_schema.referred(id)); CREATE TABLE test=> SET search_path TO public, test_schema; test=> SELECT pg_catalog.pg_get_constraintdef(r.oid, true) FROM test-> pg_catalog.pg_class c JOIN pg_catalog.pg_namespace n test-> ON n.oid = c.relnamespace test-> JOIN pg_catalog.pg_constraint r ON c.oid = r.conrelid test-> WHERE c.relname='referring' AND r.contype = 'f' test-> ; pg_get_constraintdef --------------------------------------------------- FOREIGN KEY (referred_id) REFERENCES referred(id) (1 row) Above, we created a table ``referred`` as a member of the remote schema ``test_schema``, however when we added ``test_schema`` to the PG ``search_path`` and then asked ``pg_get_constraintdef()`` for the ``FOREIGN KEY`` syntax, ``test_schema`` was not included in the output of the function. On the other hand, if we set the search path back to the typical default of ``public``:: test=> SET search_path TO public; SET The same query against ``pg_get_constraintdef()`` now returns the fully schema-qualified name for us:: test=> SELECT pg_catalog.pg_get_constraintdef(r.oid, true) FROM test-> pg_catalog.pg_class c JOIN pg_catalog.pg_namespace n test-> ON n.oid = c.relnamespace test-> JOIN pg_catalog.pg_constraint r ON c.oid = r.conrelid test-> WHERE c.relname='referring' AND r.contype = 'f'; pg_get_constraintdef --------------------------------------------------------------- FOREIGN KEY (referred_id) REFERENCES test_schema.referred(id) (1 row) SQLAlchemy will by default use the return value of ``pg_get_constraintdef()`` in order to determine the remote schema name. That is, if our ``search_path`` were set to include ``test_schema``, and we invoked a table reflection process as follows:: >>> from sqlalchemy import Table, MetaData, create_engine >>> engine = create_engine("postgresql://scott:tiger@localhost/test") >>> with engine.connect() as conn: ... conn.execute("SET search_path TO test_schema, public") ... meta = MetaData() ... referring = Table('referring', meta, ... autoload=True, autoload_with=conn) ... The above process would deliver to the :attr:`_schema.MetaData.tables` collection ``referred`` table named **without** the schema:: >>> meta.tables['referred'].schema is None True To alter the behavior of reflection such that the referred schema is maintained regardless of the ``search_path`` setting, use the ``postgresql_ignore_search_path`` option, which can be specified as a dialect-specific argument to both :class:`_schema.Table` as well as :meth:`_schema.MetaData.reflect`:: >>> with engine.connect() as conn: ... conn.execute("SET search_path TO test_schema, public") ... meta = MetaData() ... referring = Table('referring', meta, autoload=True, ... autoload_with=conn, ... postgresql_ignore_search_path=True) ... We will now have ``test_schema.referred`` stored as schema-qualified:: >>> meta.tables['test_schema.referred'].schema 'test_schema' .. sidebar:: Best Practices for PostgreSQL Schema reflection The description of PostgreSQL schema reflection behavior is complex, and is the product of many years of dealing with widely varied use cases and user preferences. But in fact, there's no need to understand any of it if you just stick to the simplest use pattern: leave the ``search_path`` set to its default of ``public`` only, never refer to the name ``public`` as an explicit schema name otherwise, and refer to all other schema names explicitly when building up a :class:`_schema.Table` object. The options described here are only for those users who can't, or prefer not to, stay within these guidelines. Note that **in all cases**, the "default" schema is always reflected as ``None``. The "default" schema on PostgreSQL is that which is returned by the PostgreSQL ``current_schema()`` function. On a typical PostgreSQL installation, this is the name ``public``. So a table that refers to another which is in the ``public`` (i.e. default) schema will always have the ``.schema`` attribute set to ``None``. .. versionadded:: 0.9.2 Added the ``postgresql_ignore_search_path`` dialect-level option accepted by :class:`_schema.Table` and :meth:`_schema.MetaData.reflect`. .. seealso:: `The Schema Search Path `_ - on the PostgreSQL website. INSERT/UPDATE...RETURNING ------------------------- The dialect supports PG 8.2's ``INSERT..RETURNING``, ``UPDATE..RETURNING`` and ``DELETE..RETURNING`` syntaxes. ``INSERT..RETURNING`` is used by default for single-row INSERT statements in order to fetch newly generated primary key identifiers. To specify an explicit ``RETURNING`` clause, use the :meth:`._UpdateBase.returning` method on a per-statement basis:: # INSERT..RETURNING result = table.insert().returning(table.c.col1, table.c.col2).\ values(name='foo') print(result.fetchall()) # UPDATE..RETURNING result = table.update().returning(table.c.col1, table.c.col2).\ where(table.c.name=='foo').values(name='bar') print(result.fetchall()) # DELETE..RETURNING result = table.delete().returning(table.c.col1, table.c.col2).\ where(table.c.name=='foo') print(result.fetchall()) .. _postgresql_insert_on_conflict: INSERT...ON CONFLICT (Upsert) ------------------------------ Starting with version 9.5, PostgreSQL allows "upserts" (update or insert) of rows into a table via the ``ON CONFLICT`` clause of the ``INSERT`` statement. A candidate row will only be inserted if that row does not violate any unique constraints. In the case of a unique constraint violation, a secondary action can occur which can be either "DO UPDATE", indicating that the data in the target row should be updated, or "DO NOTHING", which indicates to silently skip this row. Conflicts are determined using existing unique constraints and indexes. These constraints may be identified either using their name as stated in DDL, or they may be *inferred* by stating the columns and conditions that comprise the indexes. SQLAlchemy provides ``ON CONFLICT`` support via the PostgreSQL-specific :func:`_postgresql.insert()` function, which provides the generative methods :meth:`~.postgresql.Insert.on_conflict_do_update` and :meth:`~.postgresql.Insert.on_conflict_do_nothing`:: from sqlalchemy.dialects.postgresql import insert insert_stmt = insert(my_table).values( id='some_existing_id', data='inserted value') do_nothing_stmt = insert_stmt.on_conflict_do_nothing( index_elements=['id'] ) conn.execute(do_nothing_stmt) do_update_stmt = insert_stmt.on_conflict_do_update( constraint='pk_my_table', set_=dict(data='updated value') ) conn.execute(do_update_stmt) Both methods supply the "target" of the conflict using either the named constraint or by column inference: * The :paramref:`.Insert.on_conflict_do_update.index_elements` argument specifies a sequence containing string column names, :class:`_schema.Column` objects, and/or SQL expression elements, which would identify a unique index:: do_update_stmt = insert_stmt.on_conflict_do_update( index_elements=['id'], set_=dict(data='updated value') ) do_update_stmt = insert_stmt.on_conflict_do_update( index_elements=[my_table.c.id], set_=dict(data='updated value') ) * When using :paramref:`.Insert.on_conflict_do_update.index_elements` to infer an index, a partial index can be inferred by also specifying the use the :paramref:`.Insert.on_conflict_do_update.index_where` parameter:: from sqlalchemy.dialects.postgresql import insert stmt = insert(my_table).values(user_email='a@b.com', data='inserted data') stmt = stmt.on_conflict_do_update( index_elements=[my_table.c.user_email], index_where=my_table.c.user_email.like('%@gmail.com'), set_=dict(data=stmt.excluded.data) ) conn.execute(stmt) * The :paramref:`.Insert.on_conflict_do_update.constraint` argument is used to specify an index directly rather than inferring it. This can be the name of a UNIQUE constraint, a PRIMARY KEY constraint, or an INDEX:: do_update_stmt = insert_stmt.on_conflict_do_update( constraint='my_table_idx_1', set_=dict(data='updated value') ) do_update_stmt = insert_stmt.on_conflict_do_update( constraint='my_table_pk', set_=dict(data='updated value') ) * The :paramref:`.Insert.on_conflict_do_update.constraint` argument may also refer to a SQLAlchemy construct representing a constraint, e.g. :class:`.UniqueConstraint`, :class:`.PrimaryKeyConstraint`, :class:`.Index`, or :class:`.ExcludeConstraint`. In this use, if the constraint has a name, it is used directly. Otherwise, if the constraint is unnamed, then inference will be used, where the expressions and optional WHERE clause of the constraint will be spelled out in the construct. This use is especially convenient to refer to the named or unnamed primary key of a :class:`_schema.Table` using the :attr:`_schema.Table.primary_key` attribute:: do_update_stmt = insert_stmt.on_conflict_do_update( constraint=my_table.primary_key, set_=dict(data='updated value') ) ``ON CONFLICT...DO UPDATE`` is used to perform an update of the already existing row, using any combination of new values as well as values from the proposed insertion. These values are specified using the :paramref:`.Insert.on_conflict_do_update.set_` parameter. This parameter accepts a dictionary which consists of direct values for UPDATE:: from sqlalchemy.dialects.postgresql import insert stmt = insert(my_table).values(id='some_id', data='inserted value') do_update_stmt = stmt.on_conflict_do_update( index_elements=['id'], set_=dict(data='updated value') ) conn.execute(do_update_stmt) .. warning:: The :meth:`_expression.Insert.on_conflict_do_update` method does **not** take into account Python-side default UPDATE values or generation functions, e.g. those specified using :paramref:`_schema.Column.onupdate`. These values will not be exercised for an ON CONFLICT style of UPDATE, unless they are manually specified in the :paramref:`.Insert.on_conflict_do_update.set_` dictionary. In order to refer to the proposed insertion row, the special alias :attr:`~.postgresql.Insert.excluded` is available as an attribute on the :class:`_postgresql.Insert` object; this object is a :class:`_expression.ColumnCollection` which alias contains all columns of the target table:: from sqlalchemy.dialects.postgresql import insert stmt = insert(my_table).values( id='some_id', data='inserted value', author='jlh') do_update_stmt = stmt.on_conflict_do_update( index_elements=['id'], set_=dict(data='updated value', author=stmt.excluded.author) ) conn.execute(do_update_stmt) The :meth:`_expression.Insert.on_conflict_do_update` method also accepts a WHERE clause using the :paramref:`.Insert.on_conflict_do_update.where` parameter, which will limit those rows which receive an UPDATE:: from sqlalchemy.dialects.postgresql import insert stmt = insert(my_table).values( id='some_id', data='inserted value', author='jlh') on_update_stmt = stmt.on_conflict_do_update( index_elements=['id'], set_=dict(data='updated value', author=stmt.excluded.author) where=(my_table.c.status == 2) ) conn.execute(on_update_stmt) ``ON CONFLICT`` may also be used to skip inserting a row entirely if any conflict with a unique or exclusion constraint occurs; below this is illustrated using the :meth:`~.postgresql.Insert.on_conflict_do_nothing` method:: from sqlalchemy.dialects.postgresql import insert stmt = insert(my_table).values(id='some_id', data='inserted value') stmt = stmt.on_conflict_do_nothing(index_elements=['id']) conn.execute(stmt) If ``DO NOTHING`` is used without specifying any columns or constraint, it has the effect of skipping the INSERT for any unique or exclusion constraint violation which occurs:: from sqlalchemy.dialects.postgresql import insert stmt = insert(my_table).values(id='some_id', data='inserted value') stmt = stmt.on_conflict_do_nothing() conn.execute(stmt) .. versionadded:: 1.1 Added support for PostgreSQL ON CONFLICT clauses .. seealso:: `INSERT .. ON CONFLICT `_ - in the PostgreSQL documentation. .. _postgresql_match: Full Text Search ---------------- SQLAlchemy makes available the PostgreSQL ``@@`` operator via the :meth:`_expression.ColumnElement.match` method on any textual column expression. On a PostgreSQL dialect, an expression like the following:: select([sometable.c.text.match("search string")]) will emit to the database:: SELECT text @@ to_tsquery('search string') FROM table The PostgreSQL text search functions such as ``to_tsquery()`` and ``to_tsvector()`` are available explicitly using the standard :data:`.func` construct. For example:: select([ func.to_tsvector('fat cats ate rats').match('cat & rat') ]) Emits the equivalent of:: SELECT to_tsvector('fat cats ate rats') @@ to_tsquery('cat & rat') The :class:`_postgresql.TSVECTOR` type can provide for explicit CAST:: from sqlalchemy.dialects.postgresql import TSVECTOR from sqlalchemy import select, cast select([cast("some text", TSVECTOR)]) produces a statement equivalent to:: SELECT CAST('some text' AS TSVECTOR) AS anon_1 Full Text Searches in PostgreSQL are influenced by a combination of: the PostgreSQL setting of ``default_text_search_config``, the ``regconfig`` used to build the GIN/GiST indexes, and the ``regconfig`` optionally passed in during a query. When performing a Full Text Search against a column that has a GIN or GiST index that is already pre-computed (which is common on full text searches) one may need to explicitly pass in a particular PostgreSQL ``regconfig`` value to ensure the query-planner utilizes the index and does not re-compute the column on demand. In order to provide for this explicit query planning, or to use different search strategies, the ``match`` method accepts a ``postgresql_regconfig`` keyword argument:: select([mytable.c.id]).where( mytable.c.title.match('somestring', postgresql_regconfig='english') ) Emits the equivalent of:: SELECT mytable.id FROM mytable WHERE mytable.title @@ to_tsquery('english', 'somestring') One can also specifically pass in a `'regconfig'` value to the ``to_tsvector()`` command as the initial argument:: select([mytable.c.id]).where( func.to_tsvector('english', mytable.c.title )\ .match('somestring', postgresql_regconfig='english') ) produces a statement equivalent to:: SELECT mytable.id FROM mytable WHERE to_tsvector('english', mytable.title) @@ to_tsquery('english', 'somestring') It is recommended that you use the ``EXPLAIN ANALYZE...`` tool from PostgreSQL to ensure that you are generating queries with SQLAlchemy that take full advantage of any indexes you may have created for full text search. FROM ONLY ... ------------- The dialect supports PostgreSQL's ONLY keyword for targeting only a particular table in an inheritance hierarchy. This can be used to produce the ``SELECT ... FROM ONLY``, ``UPDATE ONLY ...``, and ``DELETE FROM ONLY ...`` syntaxes. It uses SQLAlchemy's hints mechanism:: # SELECT ... FROM ONLY ... result = table.select().with_hint(table, 'ONLY', 'postgresql') print(result.fetchall()) # UPDATE ONLY ... table.update(values=dict(foo='bar')).with_hint('ONLY', dialect_name='postgresql') # DELETE FROM ONLY ... table.delete().with_hint('ONLY', dialect_name='postgresql') .. _postgresql_indexes: PostgreSQL-Specific Index Options --------------------------------- Several extensions to the :class:`.Index` construct are available, specific to the PostgreSQL dialect. .. _postgresql_partial_indexes: Partial Indexes ^^^^^^^^^^^^^^^ Partial indexes add criterion to the index definition so that the index is applied to a subset of rows. These can be specified on :class:`.Index` using the ``postgresql_where`` keyword argument:: Index('my_index', my_table.c.id, postgresql_where=my_table.c.value > 10) .. _postgresql_operator_classes: Operator Classes ^^^^^^^^^^^^^^^^ PostgreSQL allows the specification of an *operator class* for each column of an index (see http://www.postgresql.org/docs/8.3/interactive/indexes-opclass.html). The :class:`.Index` construct allows these to be specified via the ``postgresql_ops`` keyword argument:: Index( 'my_index', my_table.c.id, my_table.c.data, postgresql_ops={ 'data': 'text_pattern_ops', 'id': 'int4_ops' }) Note that the keys in the ``postgresql_ops`` dictionaries are the "key" name of the :class:`_schema.Column`, i.e. the name used to access it from the ``.c`` collection of :class:`_schema.Table`, which can be configured to be different than the actual name of the column as expressed in the database. If ``postgresql_ops`` is to be used against a complex SQL expression such as a function call, then to apply to the column it must be given a label that is identified in the dictionary by name, e.g.:: Index( 'my_index', my_table.c.id, func.lower(my_table.c.data).label('data_lower'), postgresql_ops={ 'data_lower': 'text_pattern_ops', 'id': 'int4_ops' }) Operator classes are also supported by the :class:`_postgresql.ExcludeConstraint` construct using the :paramref:`_postgresql.ExcludeConstraint.ops` parameter. See that parameter for details. .. versionadded:: 1.3.21 added support for operator classes with :class:`_postgresql.ExcludeConstraint`. Index Types ^^^^^^^^^^^ PostgreSQL provides several index types: B-Tree, Hash, GiST, and GIN, as well as the ability for users to create their own (see http://www.postgresql.org/docs/8.3/static/indexes-types.html). These can be specified on :class:`.Index` using the ``postgresql_using`` keyword argument:: Index('my_index', my_table.c.data, postgresql_using='gin') The value passed to the keyword argument will be simply passed through to the underlying CREATE INDEX command, so it *must* be a valid index type for your version of PostgreSQL. .. _postgresql_index_storage: Index Storage Parameters ^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL allows storage parameters to be set on indexes. The storage parameters available depend on the index method used by the index. Storage parameters can be specified on :class:`.Index` using the ``postgresql_with`` keyword argument:: Index('my_index', my_table.c.data, postgresql_with={"fillfactor": 50}) .. versionadded:: 1.0.6 PostgreSQL allows to define the tablespace in which to create the index. The tablespace can be specified on :class:`.Index` using the ``postgresql_tablespace`` keyword argument:: Index('my_index', my_table.c.data, postgresql_tablespace='my_tablespace') .. versionadded:: 1.1 Note that the same option is available on :class:`_schema.Table` as well. .. _postgresql_index_concurrently: Indexes with CONCURRENTLY ^^^^^^^^^^^^^^^^^^^^^^^^^ The PostgreSQL index option CONCURRENTLY is supported by passing the flag ``postgresql_concurrently`` to the :class:`.Index` construct:: tbl = Table('testtbl', m, Column('data', Integer)) idx1 = Index('test_idx1', tbl.c.data, postgresql_concurrently=True) The above index construct will render DDL for CREATE INDEX, assuming PostgreSQL 8.2 or higher is detected or for a connection-less dialect, as:: CREATE INDEX CONCURRENTLY test_idx1 ON testtbl (data) For DROP INDEX, assuming PostgreSQL 9.2 or higher is detected or for a connection-less dialect, it will emit:: DROP INDEX CONCURRENTLY test_idx1 .. versionadded:: 1.1 support for CONCURRENTLY on DROP INDEX. The CONCURRENTLY keyword is now only emitted if a high enough version of PostgreSQL is detected on the connection (or for a connection-less dialect). When using CONCURRENTLY, the PostgreSQL database requires that the statement be invoked outside of a transaction block. The Python DBAPI enforces that even for a single statement, a transaction is present, so to use this construct, the DBAPI's "autocommit" mode must be used:: metadata = MetaData() table = Table( "foo", metadata, Column("id", String)) index = Index( "foo_idx", table.c.id, postgresql_concurrently=True) with engine.connect() as conn: with conn.execution_options(isolation_level='AUTOCOMMIT'): table.create(conn) .. seealso:: :ref:`postgresql_isolation_level` .. _postgresql_index_reflection: PostgreSQL Index Reflection --------------------------- The PostgreSQL database creates a UNIQUE INDEX implicitly whenever the UNIQUE CONSTRAINT construct is used. When inspecting a table using :class:`_reflection.Inspector`, the :meth:`_reflection.Inspector.get_indexes` and the :meth:`_reflection.Inspector.get_unique_constraints` will report on these two constructs distinctly; in the case of the index, the key ``duplicates_constraint`` will be present in the index entry if it is detected as mirroring a constraint. When performing reflection using ``Table(..., autoload=True)``, the UNIQUE INDEX is **not** returned in :attr:`_schema.Table.indexes` when it is detected as mirroring a :class:`.UniqueConstraint` in the :attr:`_schema.Table.constraints` collection . .. versionchanged:: 1.0.0 - :class:`_schema.Table` reflection now includes :class:`.UniqueConstraint` objects present in the :attr:`_schema.Table.constraints` collection; the PostgreSQL backend will no longer include a "mirrored" :class:`.Index` construct in :attr:`_schema.Table.indexes` if it is detected as corresponding to a unique constraint. Special Reflection Options -------------------------- The :class:`_reflection.Inspector` used for the PostgreSQL backend is an instance of :class:`.PGInspector`, which offers additional methods:: from sqlalchemy import create_engine, inspect engine = create_engine("postgresql+psycopg2://localhost/test") insp = inspect(engine) # will be a PGInspector print(insp.get_enums()) .. autoclass:: PGInspector :members: .. _postgresql_table_options: PostgreSQL Table Options ------------------------ Several options for CREATE TABLE are supported directly by the PostgreSQL dialect in conjunction with the :class:`_schema.Table` construct: * ``TABLESPACE``:: Table("some_table", metadata, ..., postgresql_tablespace='some_tablespace') The above option is also available on the :class:`.Index` construct. * ``ON COMMIT``:: Table("some_table", metadata, ..., postgresql_on_commit='PRESERVE ROWS') * ``WITH OIDS``:: Table("some_table", metadata, ..., postgresql_with_oids=True) * ``WITHOUT OIDS``:: Table("some_table", metadata, ..., postgresql_with_oids=False) * ``INHERITS``:: Table("some_table", metadata, ..., postgresql_inherits="some_supertable") Table("some_table", metadata, ..., postgresql_inherits=("t1", "t2", ...)) .. versionadded:: 1.0.0 * ``PARTITION BY``:: Table("some_table", metadata, ..., postgresql_partition_by='LIST (part_column)') .. versionadded:: 1.2.6 .. seealso:: `PostgreSQL CREATE TABLE options `_ Table values, Row and Tuple objects ----------------------------------- Row Types ^^^^^^^^^ Built-in support for rendering a ``ROW`` is not available yet, however the :func:`_expression.tuple_` may be used in its place. Another alternative is to use the :attr:`_sa.func` generator with ``func.ROW`` :: table.select().where( tuple_(table.c.id, table.c.fk) > (1,2) ).where(func.ROW(table.c.id, table.c.fk) < func.ROW(3, 7)) Will generate the row-wise comparison:: SELECT * FROM table WHERE (id, fk) > (1, 2) AND ROW(id, fk) < ROW(3, 7) .. seealso:: `PostgreSQL Row Constructors `_ `PostgreSQL Row Constructor Comparison `_ Table Types ^^^^^^^^^^^ PostgreSQL also supports passing a table as an argument to a function. This is not available yet in sqlalchemy, however the :func:`_expression.literal_column` function with the name of the table may be used in its place:: select(['*']).select_from(func.my_function(literal_column('my_table'))) Will generate the SQL:: SELECT * FROM my_function(my_table) ARRAY Types ----------- The PostgreSQL dialect supports arrays, both as multidimensional column types as well as array literals: * :class:`_postgresql.ARRAY` - ARRAY datatype * :class:`_postgresql.array` - array literal * :func:`_postgresql.array_agg` - ARRAY_AGG SQL function * :class:`_postgresql.aggregate_order_by` - helper for PG's ORDER BY aggregate function syntax. JSON Types ---------- The PostgreSQL dialect supports both JSON and JSONB datatypes, including psycopg2's native support and support for all of PostgreSQL's special operators: * :class:`_postgresql.JSON` * :class:`_postgresql.JSONB` HSTORE Type ----------- The PostgreSQL HSTORE type as well as hstore literals are supported: * :class:`_postgresql.HSTORE` - HSTORE datatype * :class:`_postgresql.hstore` - hstore literal ENUM Types ---------- PostgreSQL has an independently creatable TYPE structure which is used to implement an enumerated type. This approach introduces significant complexity on the SQLAlchemy side in terms of when this type should be CREATED and DROPPED. The type object is also an independently reflectable entity. The following sections should be consulted: * :class:`_postgresql.ENUM` - DDL and typing support for ENUM. * :meth:`.PGInspector.get_enums` - retrieve a listing of current ENUM types * :meth:`.postgresql.ENUM.create` , :meth:`.postgresql.ENUM.drop` - individual CREATE and DROP commands for ENUM. .. _postgresql_array_of_enum: Using ENUM with ARRAY ^^^^^^^^^^^^^^^^^^^^^ The combination of ENUM and ARRAY is not directly supported by backend DBAPIs at this time. Prior to SQLAlchemy 1.3.17, a special workaround was needed in order to allow this combination to work, described below. .. versionchanged:: 1.3.17 The combination of ENUM and ARRAY is now directly handled by SQLAlchemy's implementation without any workarounds needed. .. sourcecode:: python from sqlalchemy import TypeDecorator from sqlalchemy.dialects.postgresql import ARRAY class ArrayOfEnum(TypeDecorator): impl = ARRAY def bind_expression(self, bindvalue): return sa.cast(bindvalue, self) def result_processor(self, dialect, coltype): super_rp = super(ArrayOfEnum, self).result_processor( dialect, coltype) def handle_raw_string(value): inner = re.match(r"^{(.*)}$", value).group(1) return inner.split(",") if inner else [] def process(value): if value is None: return None return super_rp(handle_raw_string(value)) return process E.g.:: Table( 'mydata', metadata, Column('id', Integer, primary_key=True), Column('data', ArrayOfEnum(ENUM('a', 'b, 'c', name='myenum'))) ) This type is not included as a built-in type as it would be incompatible with a DBAPI that suddenly decides to support ARRAY of ENUM directly in a new version. .. _postgresql_array_of_json: Using JSON/JSONB with ARRAY ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Similar to using ENUM, prior to SQLAlchemy 1.3.17, for an ARRAY of JSON/JSONB we need to render the appropriate CAST. Current psycopg2 drivers accomodate the result set correctly without any special steps. .. versionchanged:: 1.3.17 The combination of JSON/JSONB and ARRAY is now directly handled by SQLAlchemy's implementation without any workarounds needed. .. sourcecode:: python class CastingArray(ARRAY): def bind_expression(self, bindvalue): return sa.cast(bindvalue, self) E.g.:: Table( 'mydata', metadata, Column('id', Integer, primary_key=True), Column('data', CastingArray(JSONB)) ) ) defaultdictN)array)hstore)json)ranges)excschema)sql)util)default) reflection)compiler)elements) expression)sqltypes)DDLBase)BIGINT)BOOLEAN)CHAR)DATE)FLOAT)INTEGER)NUMERIC)REAL)SMALLINT)TEXT)VARCHAR)UUIDz ^(?:btree|hash|gist|gin|[\w_]+)$zs\s*(?:UPDATE|INSERT|CREATE|DELETE|DROP|ALTER|GRANT|REVOKE|IMPORT FOREIGN SCHEMA|REFRESH MATERIALIZED VIEW|TRUNCATE))fallanalyseanalyzeandanyrasasc asymmetricbothcasecastcheckcollatecolumn constraintcreatecurrent_catalog current_date current_role current_timecurrent_timestamp current_userr deferrabledescdistinctdoelseendexceptfalsefetchforforeignfromgrantgrouphavingin initially intersectintoleadinglimit localtimelocaltimestampnewnotnullofoffoffsetoldononlyororderplacingprimary references returningselect session_usersome symmetrictablethentotrailingtrueunionuniqueuserusingvariadicwhenwherewindowwith authorizationbetweenbinarycrosscurrent_schemafreezefullilikeinnerisisnulljoinleftlikenaturalnotnullouteroveroverlapsrightsimilarverbose)ii)iiii)iiiceZdZdZdS)BYTEAN__name__ __module__ __qualname____visit_name__X/opt/cloudlinux/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/base.pyrrsNNNrrceZdZdZdS)DOUBLE_PRECISIONNrrrrrr'NNNrrceZdZdZdS)INETNrrrrrrNNNrrceZdZdZdS)CIDRNrrrrrrrrrceZdZdZdS)MACADDRNrrrrrrsNNNrrceZdZdZdZdS)MONEYaProvide the PostgreSQL MONEY type. Depending on driver, result rows using this type may return a string value which includes currency symbols. For this reason, it may be preferable to provide conversion to a numerically-based currency datatype using :class:`_types.TypeDecorator`:: import re import decimal from sqlalchemy import TypeDecorator class NumericMoney(TypeDecorator): impl = MONEY def process_result_value(self, value: Any, dialect: Any) -> None: if value is not None: # adjust this for the currency and numeric m = re.match(r"\$([\d.]+)", value) if m: value = decimal.Decimal(m.group(1)) return value Alternatively, the conversion may be applied as a CAST using the :meth:`_types.TypeDecorator.column_expression` method as follows:: import decimal from sqlalchemy import cast from sqlalchemy import TypeDecorator class NumericMoney(TypeDecorator): impl = MONEY def column_expression(self, column: Any): return cast(column, Numeric()) .. versionadded:: 1.2 Nrrr__doc__rrrrrrs &&PNNNrrceZdZdZdZdS)OIDzCProvide the PostgreSQL OID type. .. versionadded:: 0.9.5 Nrrrrrrs NNNrrceZdZdZdZdS)REGCLASSzHProvide the PostgreSQL REGCLASS type. .. versionadded:: 1.2.7 Nrrrrrrs  NNNrrc eZdZdfd ZxZS) TIMESTAMPFNchtt||||_dSN)timezone)superr__init__ precisionselfrr __class__s rrzTIMESTAMP.__init__s/ i''':::"rFNrrrr __classcell__rs@rrr=##########rrc eZdZdfd ZxZS)TIMEFNchtt||||_dSr)rrrrrs rrz TIME.__init__s/ dD""H"555"rrrrs@rrrrrrcdeZdZdZdZdZddZedZe dZ e dZ dS) INTERVALzPostgreSQL INTERVAL type. The INTERVAL type may not be supported on all DBAPIs. It is known to work on psycopg2 and not pg8000 or zxjdbc. TNc"||_||_dS)a Construct an INTERVAL. :param precision: optional integer precision value :param fields: string fields specifier. allows storage of fields to be limited, such as ``"YEAR"``, ``"MONTH"``, ``"DAY TO HOUR"``, etc. .. versionadded:: 1.2 N)rfields)rrrs rrzINTERVAL.__init__s# rc ,t|jS)Nr)rsecond_precision)clsintervalkws radapt_emulated_to_nativez!INTERVAL.adapt_emulated_to_natives(";<<<.processXs$ N511E rr)rdialectrs rbind_processorzUUID.bind_processorU' <     N4rc|jrd}|SdS)Nc(|t|}|Sr)rrs rrz&UUID.result_processor..processds$(//E rr)rrcoltypers rresult_processorzUUID.result_processorarrNF)rrrrrrrrrrrr!r!6sW  N        rr!ceZdZdZdZdS)TSVECTORaThe :class:`_postgresql.TSVECTOR` type implements the PostgreSQL text search type TSVECTOR. It can be used to do full text queries on natural language documents. .. versionadded:: 0.9.0 .. seealso:: :ref:`postgresql_match` Nrrrrrrqs   NNNrrceZdZdZdZfdZedZddZddZ Gdd e Z Gd d e Z d Z ddZddZddZddZxZS)ENUMa PostgreSQL ENUM type. This is a subclass of :class:`_types.Enum` which includes support for PG's ``CREATE TYPE`` and ``DROP TYPE``. When the builtin type :class:`_types.Enum` is used and the :paramref:`.Enum.native_enum` flag is left at its default of True, the PostgreSQL backend will use a :class:`_postgresql.ENUM` type as the implementation, so the special create/drop rules will be used. The create/drop behavior of ENUM is necessarily intricate, due to the awkward relationship the ENUM type has in relationship to the parent table, in that it may be "owned" by just a single table, or may be shared among many tables. When using :class:`_types.Enum` or :class:`_postgresql.ENUM` in an "inline" fashion, the ``CREATE TYPE`` and ``DROP TYPE`` is emitted corresponding to when the :meth:`_schema.Table.create` and :meth:`_schema.Table.drop` methods are called:: table = Table('sometable', metadata, Column('some_enum', ENUM('a', 'b', 'c', name='myenum')) ) table.create(engine) # will emit CREATE ENUM and CREATE TABLE table.drop(engine) # will emit DROP TABLE and DROP ENUM To use a common enumerated type between multiple tables, the best practice is to declare the :class:`_types.Enum` or :class:`_postgresql.ENUM` independently, and associate it with the :class:`_schema.MetaData` object itself:: my_enum = ENUM('a', 'b', 'c', name='myenum', metadata=metadata) t1 = Table('sometable_one', metadata, Column('some_enum', myenum) ) t2 = Table('sometable_two', metadata, Column('some_enum', myenum) ) When this pattern is used, care must still be taken at the level of individual table creates. Emitting CREATE TABLE without also specifying ``checkfirst=True`` will still cause issues:: t1.create(engine) # will fail: no such type 'myenum' If we specify ``checkfirst=True``, the individual table-level create operation will check for the ``ENUM`` and create if not exists:: # will check if enum exists, and emit CREATE TYPE if not t1.create(engine, checkfirst=True) When using a metadata-level ENUM type, the type will always be created and dropped if either the metadata-wide create/drop is called:: metadata.create_all(engine) # will emit CREATE TYPE metadata.drop_all(engine) # will emit DROP TYPE The type can also be created and dropped directly:: my_enum.create(engine) my_enum.drop(engine) .. versionchanged:: 1.0.0 The PostgreSQL :class:`_postgresql.ENUM` type now behaves more strictly with regards to CREATE/DROP. A metadata-level ENUM type will only be created and dropped at the metadata level, not the table level, with the exception of ``table.create(checkfirst=True)``. The ``table.drop()`` call will now emit a DROP TYPE for a table-level enumerated type. Tc~|dd|_tt|j|i|dS)aConstruct an :class:`_postgresql.ENUM`. Arguments are the same as that of :class:`_types.Enum`, but also including the following parameters. :param create_type: Defaults to True. Indicates that ``CREATE TYPE`` should be emitted, after optionally checking for the presence of the type, when the parent table is being created; and additionally that ``DROP TYPE`` is called when the table is dropped. When ``False``, no check will be performed and no ``CREATE TYPE`` or ``DROP TYPE`` is emitted, unless :meth:`~.postgresql.ENUM.create` or :meth:`~.postgresql.ENUM.drop` are called directly. Setting to ``False`` is helpful when invoking a creation scheme to a SQL file without access to the actual database - the :meth:`~.postgresql.ENUM.create` and :meth:`~.postgresql.ENUM.drop` methods can be used to emit SQL to a target bind. create_typeTN)poprrrr)renumsrrs rrz ENUM.__init__sC666-66"dD"E0R00000rc |d|j|d|j|d|j|d|j|d|j|dd|d|j|d i|S) zbProduce a PostgreSQL native :class:`_postgresql.ENUM` from plain :class:`.Enum`. validate_stringsnamer inherit_schemametadata_create_eventsFvalues_callabler) setdefaultrrr rrr)rimplrs rrzENUM.adapt_emulated_to_natives ($*?@@@ fdi((( h ,,, &(;<<< j$-000 &... ')=>>>syyRyyrNc\|jjsdS||j||dS)aEmit ``CREATE TYPE`` for this :class:`_postgresql.ENUM`. If the underlying dialect does not support PostgreSQL CREATE TYPE, no action is taken. :param bind: a connectable :class:`_engine.Engine`, :class:`_engine.Connection`, or similar object to emit SQL. :param checkfirst: if ``True``, a query against the PG catalog will be first performed to see if the type does not exist already before creating. N checkfirst)rsupports_native_enum _run_visitor EnumGeneratorrbindrs rr1z ENUM.creates: |0  F $,dzJJJJJrc\|jjsdS||j||dS)aEmit ``DROP TYPE`` for this :class:`_postgresql.ENUM`. If the underlying dialect does not support PostgreSQL DROP TYPE, no action is taken. :param bind: a connectable :class:`_engine.Engine`, :class:`_engine.Connection`, or similar object to emit SQL. :param checkfirst: if ``True``, a query against the PG catalog will be first performed to see if the type actually exists before dropping. Nr)rrr EnumDropperrs rdropz ENUM.drops:|0  F $*DZHHHHHrc,eZdZdfd ZdZdZxZS)ENUM.EnumGeneratorFc bttj|j|fi|||_dSr)rrrrrrr connectionrkwargsrs rrzENUM.EnumGenerator.__init__,s6 4E$$d + + 4Z J J6 J J J(DOOOrc|jsdS|j|}|jj|j|j| SNTr rr schema_for_objectrhas_typerrenumeffective_schemas r_can_create_enumz#ENUM.EnumGenerator._can_create_enum0sZ? t#@@FF .773C8 rc||sdS|jt|dSr)rr executeCreateEnumTyperrs r visit_enumzENUM.EnumGenerator.visit_enum:sA((..  O # #N4$8$8 9 9 9 9 9rr)rrrrrrrrs@rrr+s[ ) ) ) ) ) )    : : : : : : :rrc,eZdZdfd ZdZdZxZS)ENUM.EnumDropperFc bttj|j|fi|||_dSr)rrrrrr s rrzENUM.EnumDropper.__init__As6 2E$"D ) ) 2: H H H H H(DOOOrc|jsdS|j|}|jj|j|j|Sr rrs r_can_drop_enumzENUM.EnumDropper._can_drop_enumEsU? t#@@FF ?*333C4 rc||sdS|jt|dSr)rr r DropEnumTypers rrzENUM.EnumDropper.visit_enumOsA&&t,,  O # #L$6$6 7 7 7 7 7rr)rrrrrrrrs@rrr@s[ ) ) ) ) ) )    8 8 8 8 8 8 8rrc|jsdSd|vrj|d}d|jvr|jd}ntx}|jd<|j|jf|v}||j|jf|SdS)aLook in the 'ddl runner' for 'memos', then note our name in that collection. This to ensure a particular named enum is operated upon only once within any kind of create/drop sequence without relying upon "checkfirst". T _ddl_runner _pg_enumsF)rmemosetr radd)rrr ddl_runnerpg_enumspresents r_check_for_name_in_memoszENUM._check_for_name_in_memosUs 4 B  M*Jjo--%?;7:=%%?:?;7{DI.(:G LL$+ty1 2 2 2N5rFc |s|jsG|dds3|||s|||dSdSdSdSN_is_metadata_operationFrr)rgetr*r1rtargetrrrs r_on_table_createzENUM._on_table_createls  :M :7??  : // B??  : KKTjK 9 9 9 9 9 : : : : : :rc |jsE|dds1|||s|||dSdSdSdSr,)rr/r*rr0s r_on_table_dropzENUM._on_table_dropwsy  8FF3U;; 811*bAA 8 II4JI 7 7 7 7 7  8 8 8 8 8 8rc d|||s|||dSdSNr.)r*r1r0s r_on_metadata_createzENUM._on_metadata_creates@,,Z<< : KKTjK 9 9 9 9 9 : :rc d|||s|||dSdSr6)r*rr0s r_on_metadata_dropzENUM._on_metadata_drops@,,Z<< 8 II4JI 7 7 7 7 7 8 8r)NTr)rrrr native_enumrrrr1rrrrr*r2r4r7r9rrs@rrrsJKKZK11111<  [ KKKK*IIII(::::::::*88888g888*. : : : :8888::::88888888rr_arrayrrjsonb int4range int8rangenumrange daterangetsrange tstzrangeintegerbigintsmallintzcharacter varying characterz"char"rtextnumericfloatrealinetcidruuidbit bit varyingmacaddrmoneyoidregclassdouble precision timestamptimestamp with time zonetimestamp without time zone)time with time zonetime without time zonedatetimebyteabooleanrtsvectorceZdZdZdZ ddZ ddZdZdZdZ d Z d Z d Z fd Z d ZdZdZdZdZdZdZdZdZdZdZdZxZS) PGCompilerc $d|j|fi|zS)Nz ARRAY[%s])visit_clauselistrelementrs r visit_arrayzPGCompiler.visit_arrays#2T27AAbAAAArc T|j|jfi|d|j|jfi|S)N:)rstartstoprcs r visit_slicezPGCompiler.visit_slicesG DL - -" - - - - DL , , , , ,  rFc |sC|jjtjur+d|d<|jt j||jfi|Sd|d<|j||sdndfi|S)NT _cast_appliedeager_groupingz -> z ->> typerrJSONrr r,_generate_generic_binaryrrroperatorrlrs rvisit_json_getitem_op_binaryz'PGCompiler.visit_json_getitem_op_binarys E *(-??"&B 4< = =DDDD D# ,t, - z #>> rnrrs r!visit_json_path_getitem_op_binaryz,PGCompiler.visit_json_path_getitem_op_binarys E *(-??"&B 4< = =DDDD D# ,t, -z2PGCompiler.visit_empty_set_expr..sh  #,,44!&9GIIIErz WHERE 1!=1)r{r)r element_typess` rvisit_empty_set_exprzPGCompiler.visit_empty_set_exprs_ II +9wyyk       rctt|||}|jjr|dd}|S)N\z\\)rr`rr_backslash_escapesreplace)rrrrs rrzPGCompiler.render_literal_value(sGj$''<!>s!C!CCCrc d}|j|d|j|jfi|zz }|j%|j|dz }|d|j|jfi|zz }|S)Nrz LIMIT z LIMIT ALLz OFFSET ) _limit_clauser_offset_clause)rr^rrGs r limit_clausezPGCompiler.limit_clause2s}   + L<4<0D#K#K#K#KK KD  ,#+' Jf.C!J!Jr!J!JJ JD rcj|dkrtjd|zd|zS)NONLYzUnrecognized hint: %rzONLY )upperr CompileError)rsqltextrbhintiscruds rformat_from_hint_textz PGCompiler.format_from_hint_text<s7 ::<<6 ! !"#:T#ABB B  rc |jdurr|jdurdSt|jttfr-ddfd|jDzdzSdj|jfizdzSdS) NFTz DISTINCT z DISTINCT ON (rc,g|]}j|fiSrr)rcolrrs r z4PGCompiler.get_select_precolumns..Is-MMMSc00R00MMMrz) r) _distinct isinstancelisttupler{r)rr^rs` `rget_select_precolumnsz PGCompiler.get_select_precolumnsAs  5 ( (4''"{F,tUm<< #iiMMMMMF.hsR&& UH4EHHRHH&&&&&&rz NOWAITz SKIP LOCKED) _for_update_argread key_sharerRr OrderedSetupdatesql_utilsurface_selectables_onlyr{nowait skip_locked)rr^rtmptablescs` ` rfor_update_clausezPGCompiler.for_update_clauseVs  ! & %/ #&"  # - &CCC  ! $ _&&F+. D D h?BBCCCC 6DII&&&&&#&&& C  ! (  9 C  ! - " > !C rctfdtj|D}dd|zS)Nc Bg|]}d|ddiS)NTF)_label_select_columnrrrs rrz/PGCompiler.returning_clause..vs?     % %dAtUB ? ?   rz RETURNING r)r_select_iterablesr{)rstmtreturning_colscolumnss` rreturning_clausezPGCompiler.returning_clausetsO    1.AA    dii0000rc |j|jjdfi|}|j|jjdfi|}t|jjdkr*|j|jjdfi|}d|d|d|dSd|d|dS)Nrrz SUBSTRING(z FROM z FOR r)rclauseslen)rfuncrsrhrs rvisit_substring_funczPGCompiler.visit_substring_func}s DL-a0 7 7B 7 7 T\1!4;;;; t|# $ $q ( (!T\$,"6q"9@@R@@FF56QQvvvF F )/0aa7 7rc |j d|jz}n]|jTddfd|jDz}|j#|d|jddzz }nd}|S) NzON CONSTRAINT %s(%s)rc3K|]P}t|tjrj|n|ddVQdS)F include_tablerN)rr string_typesrquoterrs rrz1PGCompiler._on_conflict_target..sv-- "!T%677PDM''***auOO ------r WHERE %sFrr)constraint_targetinferred_target_elementsr{inferred_target_whereclauser)rclauser target_texts` r_on_conflict_targetzPGCompiler._on_conflict_targets  # /,v/GGKK  , 8 499----  8 ---$$K1={T\\6"'$.:..  Krc 0|j|fi|}|rd|zSdS)NzON CONFLICT %s DO NOTHINGzON CONFLICT DO NOTHING)r)r on_conflictrrs rvisit_on_conflict_do_nothingz'PGCompiler.visit_on_conflict_do_nothings5.d.{AAbAA  ,.< <++rc |}|j|fi|}g}t|j}|jdd}|jj}|D]} | j} | |vr|| } tj | rtj d| | j } nFt| tj r,| j j r | } | j | _ || d} |j| } || d| |rt)jd|jjjdd d |D|D]\}}t|t(jr|j|n||d} |tj|d} || d| d |}|j#|d ||jd d zz }d|d|S)N selectablerF)rz = z?Additional column names not matching any column keys in table 'z': rc3 K|] }d|zV dSz'%s'Nr)rrs rrz9PGCompiler.visit_on_conflict_do_update..s&BBavzBBBBBBrrTrz ON CONFLICT z DO UPDATE SET )rdictupdate_values_to_setstackrbrkeyrr _is_literal BindParameterrorr_cloner self_grouprrappendrwarncurrent_executablerr{itemsr_literal_as_bindsupdate_whereclause)rrrrraction_set_opsset_parametersinsert_statementcolsrcol_keyr value_textkey_textkv action_texts rvisit_on_conflict_do_updatez&PGCompiler.visit_on_conflict_do_updates.d.{AAbAA f9:: :b>,7%' J JAeG.((&**733'.. ,$24afMMMEE#5(*@AA,!J.,!& %&V !\\%*:*:*<*<\OO =..w77%%888ZZ&HIII  J II+1666YYBB>BBBBBB    ',,.. J J1"!T%677;DM''***aE:: "\\.q11e* %%888ZZ&HIIIIii//  $ 0 ;)%*6** K5@KKMMrc Tddfd|DzS)NzFROM rc3:K|]}|jfddVdST)asfrom fromhintsN_compiler_dispatchrt from_hintsrrs rrz0PGCompiler.update_from_clause..sS# #  !A  Odj O OB O O# # # # # # rr{)r update_stmt from_table extra_fromsrrs` ``rupdate_from_clausezPGCompiler.update_from_clausesT# # # # # #  # # #     rc Tddfd|DzS)z9Render the DELETE .. USING clause specific to PostgreSQL.zUSING rc3:K|]}|jfddVdSr rrs rrz6PGCompiler.delete_extra_from_clause..sS$ $  !A  Odj O OB O O$ $ $ $ $ $ rr)r delete_stmtrrrrs` ``rdelete_extra_from_clausez#PGCompiler.delete_extra_from_clausesT$))$ $ $ $ $ $  $ $ $     rr)rrrrerjrtrvrzr}rrrrrrrrrrrrrrrrrrrs@rr`r`sBBB   /4    "/4                         DDD!!! *<1118880,,,;N;N;Nz          rr`cTeZdZdZfdZdZdZdZdZdZ dZ d Z d Z xZ S) PGDDLCompilerc (|j|}|j|j}t |t jr|j}|j r||j j ur|jj st |t j sx|j+t |jtjrR|jjrFt |t jr|dz }nwt |t j r|dz }nW|dz }nQ|d|jj|j||jzz }||}||d|zz }|j |d||jzz }|js|dz }|S)Nz BIGSERIALz SMALLSERIALz SERIAL )type_expressionidentifier_preparerz DEFAULT z NOT NULL)r format_columnro dialect_implrrr TypeDecoratorr primary_keyrb_autoincrement_columnsupports_smallserial SmallIntegerrr Sequenceoptional BigIntegerrrget_column_default_stringcomputednullable)rr/r colspec impl_typers rget_column_specificationz&PGDDLCompiler.get_column_specifications---f55K,,T\:: i!7 8 8 '!I   1&,<<< 1=")X-BCC= &v~v??'/')X%899 %<'Ix'<== %>)9$ sT\7?? &$(M@ G 44V<.>sU!))#+a..)MMrr)rdr format_typer{r)rr1rs` rvisit_create_enum_typez$PGDDLCompiler.visit_create_enum_type9st M % %e , , , , II      rcJ|j}d|j|zS)Nz DROP TYPE %s)rdrrC)rrrs rvisit_drop_enum_typez"PGDDLCompiler.visit_drop_enum_typeDs$ !:!:5!A!ABBrc j}|j}|d}|jr|dz }|dz }jjr|jdd}|r|dz }||dd ||j d z }|jdd }|r8|d j |t zz }|jdd  |dd fd|jDzz }|jdd}|r7|dd d|Dzz }|jdd}|r|d||zz }|jdd} | %j| dd} |d| zz }|S)NzCREATE zUNIQUE zINDEX postgresql concurrently CONCURRENTLY Finclude_schemaz ON rrjz USING %s opsrrcg|]y}jt|tjs|n|ddt |dr|jvrd|jzndzzS)FTrr?rrr)r@rrr ColumnClauserhasattrr)rexprrMrs rrz4PGDDLCompiler.visit_create_index..fs%--)$ 0GHH")))!&+&* .#4// 48HOOs48},, rroz WITH (%s)cg|]}d|zS)z%s = %sr)rstorage_parameters rrz4PGDDLCompiler.visit_create_index..}s.-"$55r tablespacez TABLESPACE %srmTrOz WHERE )rrd_verify_index_tablerhr#_supports_create_index_concurrentlydialect_options_prepared_index_namer:rbvalidate_sql_phrase IDX_USINGlowerr{ expressionsrrr@r) rr1rindexrGrIrj withclausetablespace_name whereclausewhere_compiledrMs ` @rvisit_create_indexz PGDDLCompiler.visit_create_indexIse=   ''' <  I D  < ; ( 0>~NL ('  % %eE % B B B B  ! !%+ . . . .   %l3G<   -33E9EEKKMMN D #L1%8  II!& 1    (*<8@   L 1;1A1A1C1C D / =lK  G $x~~o'F'FF FD+L9'B  "!.6657N I. .D rc|j}d}|jjr|jdd}|r|dz }|||dz }|S)Nz DROP INDEX rHrIrJTrK)rdr!_supports_drop_index_concurrentlyrXrY)rrr^rGrIs rvisit_drop_indexzPGDDLCompiler.visit_drop_indexsa  < 9 ( 0>~NL (' ))%)EEE rc rd}|j |d|j|zz }g}|jD]i\}}}d|d<|jj|fi|t |dr#|j|jvrd|j|jzndz}|j |d|j|d|j |j t d d |d z }|j'|d |j|jd zz }|||z }|S)NrzCONSTRAINT %s Frrrz WITH zEXCLUDE USING z (rrz WHERE (%s)Tr>)rrformat_constraint _render_exprsr@rrQrrMrrZrjr[r\r{rmdefine_constraint_deferrability) rr0rrGrrRropexclude_elements rvisit_exclude_constraintz&PGDDLCompiler.visit_exclude_constraints ? & $t}'F'F(( D(6 B BND$"'B 7d/7CCCC4'',0H ,F,Fz~dh///O HOOOORR@ A A A A  M - - )  egg   IIh          ' MD$5$=$= %>%% D 44Z@@@ rcg}|jd}|d}|Yt|ttfs|f}|ddfd|Dzdz|dr|d|dz|d d ur|d n|d d ur|d |drF|ddd}|d|z|dr8|d}|dj |zd|S)NrHinheritsz INHERITS ( rc3LK|]}j|VdSr)rr)rrrs rrz2PGDDLCompiler.post_create_table..s3KK$DM//55KKKKKKrz ) partition_byz PARTITION BY %s with_oidsTz WITH OIDSFz WITHOUT OIDS on_commit_rz ON COMMIT %srUz TABLESPACE %sr) rXr/rrrrr{rrrr)rrb table_optspg_optsroon_commit_optionsr`s` rpost_create_tablezPGDDLCompiler.post_create_tables ' 5;;z**  hu 66 '$;    ))KKKK(KKKKKL    > " N   2W^5LL M M M ; 4 ' '   n - - - - [ !U * *   / 0 0 0 ;  E ' 4 <  < # C%,& &D ? & Geo- -D rc V|jrd}|j |d|jzz }n d|jz}|S)Nz BIT VARYINGrzBIT(%d))rr)rrrcompileds r visit_BITzPGTypeCompiler.visit_BITO s< = 0$H|'FU\11 5</Hrc dS)Nr!rrs r visit_UUIDzPGTypeCompiler.visit_UUIDX rrc |j|fi|Sr) visit_BYTEArs rvisit_large_binaryz!PGTypeCompiler.visit_large_binary[ st,,,,,rc dS)Nrrrs rrzPGTypeCompiler.visit_BYTEA^ rrc ||j}tjddd|j|jndzz|dS)Nz((?: COLLATE.*)?)$z%s\1[]r)count)rr5resub dimensions)rrrrxs r visit_ARRAYzPGTypeCompiler.visit_ARRAYa s_ U_--v !+0+;+Gu''QP     rr)"rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrs@rr~r~sKKK """11100000 6666       ---       rr~c eZdZeZdZddZdS)PGIdentifierPreparercx|d|jkr(|dd|j|j}|S)Nrrr) initial_quoterescape_to_quote escape_quote)rrs r_unquote_identifierz(PGIdentifierPreparer._unquote_identifierw sC 8t) ) )!B$K''$d&7E rTc|jstjd||j}||}|js|r|||dz|z}|S)Nz%PostgreSQL ENUM type requires a name..)rr rrr omit_schema quote_schema)rrrrrs rrCz PGIdentifierPreparer.format_type~ sz L"#JKK Kzz%*%%11%88  D D!,$$%566&FL,N"N"N$( >)>)K( >++&"7";;V['*(/5~/F(B%:HH%BBB ,+C +Ca"s1rCHH}'>'>">>?Ca"s1rCHH}'>'>">>?C*-##sss3D=AAF/((( B<+'+'H'H (($$(,$#//((( CC0 9ABC++C==='..AA&IIIs4A<e  !!"6== %)$<$F!( * M..00DM M  hmT 2 2 2 M  dD ) ) )%)$<$F!  $v - N  !CDDM   $ . 0261IN 2 ...rc$jfd}|SdS)Nc>|jdSr)set_isolation_levelr)rrs rconnectz%PGDialect.on_connect..connect s"((t/CDDDDDr)r)rr3s` r on_connectzPGDialect.on_connect s6   + E E E E EN4r) SERIALIZABLEzREAD UNCOMMITTEDzREAD COMMITTEDzREPEATABLE READc b|dd}||jvr:tjd|d|jdd|j|}|d|z|d|dS) NrtrzInvalid value 'z2' for isolation_level. Valid isolation levels for z are rz=SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL %sCOMMIT) r_isolation_lookupr ArgumentErrorrr{cursorrclose)rr levelr:s rr2zPGDialect.set_isolation_level s c3'' . . .##55$)))TYYt/E%F%F%FH  ""$$ !#( )    x    rc|}|d|d}||S)Nz show transaction isolation levelr)r:rfetchoner;r)rr r:vals rget_isolation_levelzPGDialect.get_isolation_level sU""$$9:::oo" yy{{rc:||jdSr)do_beginr rr xids rdo_begin_twophasezPGDialect.do_begin_twophase s j+,,,,,rc6|d|zdS)NzPREPARE TRANSACTION '%s')rrCs rdo_prepare_twophasezPGDialect.do_prepare_twophase s"5;<<<< > >   w ' ' '   Z2 3 3 3 3 3   Z2 3 3 3 3 3rc|r`|r|d|d|z|d||jdS||jdS)NrIzCOMMIT PREPARED '%s'rJ)rrKr  do_commitrLs rdo_commit_twophasezPGDialect.do_commit_twophase s  2 /"":...   5; < < <   w ' ' '   Z2 3 3 3 3 3 NN:0 1 1 1 1 1rch|tjd}d|DS)Nz!SELECT gid FROM pg_prepared_xactscg|] }|d Srr)rrows rrz1PGDialect.do_recover_twophase.. s,,,3A,,,r)rr rG)rr  resultsets rdo_recover_twophasezPGDialect.do_recover_twophase s;&& H8 9 9  -,),,,,rc,|dS)Nzselect current_schema())r/)rr s r_get_default_schema_namez"PGDialect._get_default_schema_name s  !:;;;rc 8d}|tj|tjdt j|jtj }t| S)Nz=select nspname from pg_namespace where lower(nspname)=:schemar r) rr rG bindparams bindparamrrr\rUnicodeboolfirst)rr r queryr:s r has_schemazPGDialect.has_schema s N ## HUOO & & N<6<>>22"*    FLLNN###rc Z|l|tjdtjdt j|tj}n|tjdtjdt j|tjtjdt j|tj}t| S)Nzselect relname from pg_class c join pg_namespace n on n.oid=c.relnamespace where pg_catalog.pg_table_is_visible(c.oid) and relname=:namerrztselect relname from pg_class c join pg_namespace n on n.oid=c.relnamespace where n.nspname=:schema and relname=:namer rr rGr\r]rrrr^r_r`)rr rr r:s r has_tablezPGDialect.has_table s >''( *Mz22&.  FF ''$*Mz22&. M v..&.   F$FLLNN###rc Z|l|tjdtjdt j|tj}n|tjdtjdt j|tjtjdt j|tj}t| S)NzSELECT relname FROM pg_class c join pg_namespace n on n.oid=c.relnamespace where relkind='S' and n.nspname=current_schema() and relname=:namerrzSELECT relname FROM pg_class c join pg_namespace n on n.oid=c.relnamespace where relkind='S' and n.nspname=:schema and relname=:namer rd)rr  sequence_namer r:s r has_sequencezPGDialect.has_sequence s >''( *M}55&.  FF '':*M}55&. M v..&.   F&FLLNN###rc|d}tj|}nd}tj|}|tjdt j|t j}|F|tjdt j|t j}||}t| S)Na  SELECT EXISTS ( SELECT * FROM pg_catalog.pg_type t, pg_catalog.pg_namespace n WHERE t.typnamespace = n.oid AND t.typname = :typname AND n.nspname = :nspname ) z SELECT EXISTS ( SELECT * FROM pg_catalog.pg_type t WHERE t.typname = :typname AND pg_type_is_visible(t.oid) ) typnamernspname) r rGr\r]rrrr^rr_r/)rr  type_namer rar:s rrzPGDialect.has_type4 s  EHUOOEEEHUOOE  M4>)44H.a sHHH!-c!ff---rrrr )rr/rrAssertionErrorrrE)rr rms r_get_server_version_infoz"PGDialect._get_server_version_infoV s   1 2 2 9 9 ; ; H C      >B HHaggaA&6&6HHHIIIrc d}|d}nd}d|z}tj|}|tj|}tj|t j}|t j}|r3|tj dt j}| ||| } | }|tj ||S) zFetch the oid for schema.table_name. Several reflection methods require the table oid. The idea for using this method is that it can be fetched one time and cached for subsequent calls. Nzn.nspname = :schemaz%pg_catalog.pg_table_is_visible(c.oid)a  SELECT c.oid FROM pg_catalog.pg_class c LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace WHERE (%s) AND c.relname = :table_name AND c.relkind in ('r', 'v', 'm', 'f', 'p') )r)rRr r)rr )rrr rGr\rr^rIntegerr]rr/r NoSuchTableError) rr rr r table_oidschema_where_clauserarrs rrzPGDialect.get_table_oidc s  "7  "I  " " ^J//  ^F++F HUOO & &(2B & C C II(*I + +  N S]88;KLLLMMA   qZ  G GHHJJ  &z22 2rc |tjdtj}d|DS)NzOSELECT nspname FROM pg_namespace WHERE nspname NOT LIKE 'pg_%' ORDER BY nspname)rkcg|]\}|Srrrrs rrz.PGDialect.get_schema_names.. ))))))r)rr rGrrr^)rr rresults rget_schema_nameszPGDialect.get_schema_names sU## H#  gh.g//   *)&))))rc |tjdtj||n|j}d|DS)NzSELECT c.relname FROM pg_class c JOIN pg_namespace n ON n.oid = c.relnamespace WHERE n.nspname = :schema AND c.relkind in ('r', 'p')relnamer cg|]\}|Srrr{s rrz-PGDialect.get_table_names.. r|rrr rGrrr^rrr r rr}s rget_table_nameszPGDialect.get_table_names sj## HH  gh.g//#/66T5M $  *)&))))rc |tjdtj||n|j}d|DS)Nz|SELECT c.relname FROM pg_class c JOIN pg_namespace n ON n.oid = c.relnamespace WHERE n.nspname = :schema AND c.relkind = 'f'rr cg|]\}|Srrr{s rrz6PGDialect._get_foreign_table_names.. r|rrrs rrz"PGDialect._get_foreign_table_names sj## H@  gh.g//#/66T5M $  *)&))))rrc ddd fdtj|D}n!#t$rtd|dwxYw|std|t jdd d |Dztj ||n|j }d |DS)Nrrrrc g|] }| Srr)ri include_kinds rrz,PGDialect.get_view_names.. sDDD\!_DDDrzinclude zU unknown, needs to be a sequence containing one or both of 'plain' and 'materialized'zZempty include, needs to be a sequence containing one or both of 'plain' and 'materialized'z~SELECT c.relname FROM pg_class c JOIN pg_namespace n ON n.oid = c.relnamespace WHERE n.nspname = :schema AND c.relkind IN (%s)rc3 K|] }d|zV dSrr)relems rrz+PGDialect.get_view_names.. s&==tVd]======rrr cg|]\}|Srrr{s rrz,PGDialect.get_view_names.. r|r) rto_listKeyError ValueErrorrr rGr{rrr^r)rr r rrkindsr}rs @rrzPGDialect.get_view_names s( "%c::  DDDDdl7.C.CDDDEE   *?FwwI    <  ## HB99==u=====?   gh.g//#/66T5M$  *)&))))s )Ac |tjdtj||n|j|}|S)NzSELECT pg_get_viewdef(c.oid) view_def FROM pg_class c JOIN pg_namespace n ON n.oid = c.relnamespace WHERE n.nspname = :schema AND c.relname = :view_name AND c.relkind IN ('v', 'm'))view_def)r view_name)r/r rGrrr^r)rr rr rrs rget_view_definitionzPGDialect.get_view_definition s]$$ H.   gx/g00#/66T5M%   rc |||||d}|jdkrdnd}d|z}tj|tjdtj tj tj }| || } | } | |} td ||d D} g} | D]=\}}}}}}}}|||||| | ||| }| |>| S)Nrr) za.attgenerated as generatedzNULL as generateda SELECT a.attname, pg_catalog.format_type(a.atttypid, a.atttypmod), (SELECT pg_catalog.pg_get_expr(d.adbin, d.adrelid) FROM pg_catalog.pg_attrdef d WHERE d.adrelid = a.attrelid AND d.adnum = a.attnum AND a.atthasdef) AS DEFAULT, a.attnotnull, a.attnum, a.attrelid as table_oid, pgd.description as comment, %s FROM pg_catalog.pg_attribute a LEFT JOIN pg_catalog.pg_description pgd ON ( pgd.objoid = a.attrelid AND pgd.objsubid = a.attnum) WHERE a.attrelid = :table_oid AND a.attnum > 0 AND NOT a.attisdropped ORDER BY a.attnum rwr)attnamerrwc3`K|])}|dr |df|fn|d|df|fV*dS)visiblerr Nr)rrecs rrz(PGDialect.get_columns.. sf  9~ 5c&k^S ! !x=#f+.4      r*r )rr/r+r rGr\r]rrurr^rfetchall _load_domainsrr_get_column_infor)rr rr rrwr{SQL_COLSrrrowsdomainsrrrrCdefault_rattnumcomment column_infos r get_columnszPGDialect.get_columns s&&  Frvvl7K7K'  '500 * )$   $%  , HX   Z k9IJJJ K K WX-x7GW H H   qI  6 6zz||$$Z00  '' 3'??       ( (        //  K NN; ' ' ' 'rc d} tjdd|} | | \} } ttj| } | }tjd|}|r|d}tjd|}|rK|dr6ttjd|d}nd}i}| d kr<|r7|d \}}t|t|f}nd}n| d krd }n| d krd}n| dvrd|d<|rt||d<d}n| dvrd|d<|rt||d<d}n| dkrd|d<|rt|f}n}d}nz| drStj d| tj }|rt||d<|r|d|d<d} d}n|rt|f} | |j vr|j | }n| |vrC|| }t}|d|d<|ds |d|d<t|d}nc| |vr\|| }|d} | | \} } ttj| } |o|d}|dr |s|d}d} |r!||i|}| r|j d |}n'tjd!| d"|d#tj}| rt#|| d$k%}d}nd}d}|tjd&|}|t%|jtjrd}|}d'|d(vrL|J|dd)|zzd'z|d(z|d*z}t#||||||+}|||d,<|S)-NcXtjdd||dfS)Nz\[\]$rr)rrendswith)attypes r_handle_array_typez6PGDialect._get_column_info.._handle_array_type7 s.xV,,%% rz\(.*\)rz \(([\d,]+)\)rz\((.*)\)\s*,\s*rrH,rT)5rC)rVrXTrr)rWrYr[FrOrrz interval (.+)rrrr labelsrr.rr;zDid not recognize type 'z ' of column ''r)rrzz(nextval\(')([^']+)('.*$)rrz"%s"r )rror.r autoincrementrr-)rrrrquoted_token_parsersearchrEsplitro startswithrI ischema_namesrrrNULLTYPEr issubclassrru)rrrCrrrrr rr{rris_arrayenum_or_domain_keyr.charlenargsr precscale field_matchrrdomainr-rrschrs rrzPGDialect._get_column_info+ s    2{33.-f55#4#;F#C#CDD;)O[99  'mmA&&Gyk22  DJJqMM *djjmm<<==DDD Y   %mmC00 eD 3u::. ) ) )DD y DD J J J!%F:  3&)'ll{#DD    "'F:  3&)'ll{#DD } $ $ $F9  G    z * * #(#3VRTBBK 3&)'ll{# 8#.#4#4Q#7#7x FDD  #LL?D +++,V4#u,,/0!%fvI6'+H~F8$T(^,,#w.. !34)#5#5f#=#= %*4+CF+K+K%L%L"$:z(:)$0W0%Y/G  (gt.v..G @6$,X6w?? II@FM   'G  GyC7GHHHHGGH  I>HHE g4h6FGG)$(Mekk!nn,,  A!C<) ++a..) ++a.. )'      &.K #rc >|||||d}|jdkrd|ddz}nd}t j|tj}| || }d | D} d } t j| tj }| || }| } | | d S)Nrr)r&aq SELECT a.attname FROM pg_class t join pg_index ix on t.oid = ix.indrelid join pg_attribute a on t.oid=a.attrelid AND %s WHERE t.oid = :table_oid and ix.indisprimary = 't' ORDER BY a.attnum a.attnum ix.indkeya SELECT a.attname FROM pg_attribute a JOIN ( SELECT unnest(ix.indkey) attnum, generate_subscripts(ix.indkey, 1) ord FROM pg_index ix WHERE ix.indrelid = :table_oid AND ix.indisprimary ) k ON a.attnum=k.attnum WHERE a.attrelid = :table_oid ORDER BY k.ord rrcg|] }|d SrUr)rrs rrz/PGDialect.get_pk_constraint.. s+++!+++rz SELECT conname FROM pg_catalog.pg_constraint r WHERE r.conrelid = :table_oid AND r.contype = 'p' ORDER BY 1 )conname)constrained_columnsr) rr/r+ _pg_index_anyr rGrrr^rrr/) rr rr rrwPK_SQLrrr PK_CONS_SQLrs rget_pk_constraintzPGDialect.get_pk_constraint s'&&  Frvvl7K7K'    #f , , $$K FF" F HV   $ $X-= $ > >   qI  6 6++ajjll+++ H[ ! ! ) )(2B ) C C   qI  6 6xxzz'+T:::rc b|j|||||d}d}tjd}t j|tj tj } | | |} g} | D]\} } }tj ||  }|\ }}}}}}}}}}}}}| |dkrdnd }fd tjd |D}|r||jkr|}n%|}n"|r|}n |||kr|}|}fd tjd |D}| |||||||||dd}| || S)Nrra SELECT r.conname, pg_catalog.pg_get_constraintdef(r.oid, true) as condef, n.nspname as conschema FROM pg_catalog.pg_constraint r, pg_namespace n, pg_class c WHERE r.conrelid = :table AND r.contype = 'f' AND c.oid = confrelid AND n.oid = c.relnamespace ORDER BY 1 a/FOREIGN KEY \((.*?)\) REFERENCES (?:(.*?)\.)?(.*?)\((.*?)\)[\s]?(MATCH (FULL|PARTIAL|SIMPLE)+)?[\s]?(ON UPDATE (CASCADE|RESTRICT|NO ACTION|SET NULL|SET DEFAULT)+)?[\s]?(ON DELETE (CASCADE|RESTRICT|NO ACTION|SET NULL|SET DEFAULT)+)?[\s]?(DEFERRABLE|NOT DEFERRABLE)?[\s]?(INITIALLY (DEFERRED|IMMEDIATE)+)?)rcondef)rb DEFERRABLETFc:g|]}|Srrrrprs rrz.PGDialect.get_foreign_keys..D s7###,,Q//###rrc:g|]}|Srrrs rrz.PGDialect.get_foreign_keys..[ s7   ,,Q//   rz\s*,\s)onupdateondeleter8rHr)rrreferred_schemareferred_tablereferred_columnsoptions)r!rr/rcompiler rGrrr^rrrgroupsrrrr)rr rr rrrwFK_SQLFK_REGEXrrfkeysrr conschemarrrrrrrtrrrr8rHfkey_drs @rget_foreign_keyszPGDialect.get_foreign_keys sa+&&  Frvvl7K7K'    : 7    HV   $ $$X-= %     q  2 2*+**,,> !> ! &GVY (F++2244A  # %%/<%?%?TTU ####*.ABB###  - ) 888&/OO&,OO  )#+">">"O"O#)(;(;#)%99.IIN    )-=>>      ':#2"0$4 ( (",!*"   F LL  rc|jdkr3ddfdtddDzSddS) N)r&rrz OR c3(K|] }d|fzV dS)z %s[%d] = %sNr)rindr compare_tos rrz*PGDialect._pg_index_any..x s@((;> S# 66((((((rr z = ANY(r)r+r{range)rrrs ``rrzPGDialect._pg_index_anyp sy  #f , ,FKK(((((BG2,,((( &)SS***5 5rc "|||||d}|jdkrKd|jdkrdndd|jdkrd nd d |jd krd nd d|ddd }nd|jdkrdnd d}t j|tjtj}| ||}td} d} | D]t} | \ } } }}}}}}}}}}|r | | krtj d| z| } 4|r| | kstj d| z| } | | v}| | }| ||d|<|s|}|r,||dr"tj d| d|d|}d|D|d<i}t|pdD]N\}}t!|}d }|d!zr|d"z }|d#zs|d$z }n |d#zr|d%z }|r|||<O|r||d&<| |d'<|| |d(<|rt%d)|D|d*<|r |d+kr||d,<vg}| D]\} "| "d'"fd-"dDd.}!d("vr "d(|!d(<d&"vr6t%"fd/"d&D|!d0<d*"vr"d*|!d1id2<d,"vr"d,|!d1id3<||!|S)4Nrr)r&z SELECT i.relname as relname, ix.indisunique, ix.indexprs, ix.indpred, a.attname, a.attnum, NULL, ix.indkeyr(z ::varcharrz, zix.indoption::varcharNULLrr%z i.reloptionsam, am.amname, NULL as indnkeyatts FROM pg_class t join pg_index ix on t.oid = ix.indrelid join pg_class i on i.oid = ix.indexrelid left outer join pg_attribute a on t.oid = a.attrelid and rraw left outer join pg_am am on i.relam = am.oid WHERE t.relkind IN ('r', 'v', 'f', 'm') and t.oid = :table_oid and ix.indisprimary = 'f' ORDER BY t.relname, i.relname a SELECT i.relname as relname, ix.indisunique, ix.indexprs, ix.indpred, a.attname, a.attnum, c.conrelid, ix.indkey::varchar, ix.indoption::varchar, i.reloptions, am.amname, ) rzix.indnkeyattsa as indnkeyatts FROM pg_class t join pg_index ix on t.oid = ix.indrelid join pg_class i on i.oid = ix.indexrelid left outer join pg_attribute a on t.oid = a.attrelid and a.attnum = ANY(ix.indkey) left outer join pg_constraint c on (ix.indrelid = c.conrelid and ix.indexrelid = c.conindid and c.contype in ('p', 'u', 'x')) left outer join pg_am am on i.relam = am.oid WHERE t.relkind IN ('r', 'v', 'f', 'm', 'p') and t.oid = :table_oid and ix.indisprimary = 'f' ORDER BY t.relname, i.relname )rrrc*ttSrrrrrrz'PGDialect.get_indexes.. k$&7&7rz;Skipped unsupported reflection of expression-based index %sz7Predicate of partial index %s ignored during reflectionrz#INCLUDE columns for covering index z ignored during reflectioncPg|]#}t|$Sr)rostrip)rrs rrz)PGDialect.get_indexes.. s&AAA1AGGIIAAArrrr)r9r) nullslast) nullsfirstsortingrhduplicates_constraintc8g|]}|dS)=)r)roptions rrz)PGDialect.get_indexes..&s$AAAvc**AAArrbtreeamnamec,g|]}d|Srr)rridxs rrz)PGDialect.get_indexes..5s! D D DAVQ D D Dr)rrh column_namesc3VK|]#\}}dd||fV$dS)rrNr)rrrrs rrz(PGDialect.get_indexes..:sQ// 5[UA/7//////rcolumn_sortingrXpostgresql_withpostgresql_using)rr/r+rr rGrrr^rrrrrr enumeraterorrrrr)#rr rr rrwIDX_SQLrrindexes sv_idx_namerVidx_namerhrRprdrcol_numconrelididx_key idx_optionrr indnkeyattshas_idxr^idx_keysrcol_idx col_flags col_sortingr}rentryrs# @r get_indexeszPGDialect.get_indexes~ s.&&  Frvvl7K7K'    #f , , ,: $76AA rII+v55('+v55"":{;;;;G$GG -L+w66! =!GF HW   % %$h.> &     qI  6 67788 ::<<U -U -C  {**I46>?'  '8{22 M' ')GH%E),f g&1 -"==??68KLL#96II7?xxB (  5HAAAAAe *3%2,,..++77&GY!$IOO$5$5 6 6I"$K 4';#y0 )D 0:'>9K$t+;'?:K"7+6(/'.E)$"(h'5=E12'+AAAAA((E)$-f//&,E(O  ! !ID#h- D D D DU D D DE '#--145L1M-.C*.////$' N$8$8$:$:///++&'C N  !2B77%3M  !2B77& MM%  rc |||||d}d}tj|t j}|||}td} | D].} | | j } | j | d<| j | d| j </d | DS) Nrra SELECT cons.conname as name, cons.conkey as key, a.attnum as col_num, a.attname as col_name FROM pg_catalog.pg_constraint cons join pg_attribute a on cons.conrelid = a.attrelid AND a.attnum = ANY(cons.conkey) WHERE cons.conrelid = :table_oid AND cons.contype = 'u' )col_namerc*ttSrrrrrrz2PGDialect.get_unique_constraints..drrrrcDg|]\}|fddDdS)c,g|]}d|Srr)rrucs rrz?PGDialect.get_unique_constraints...ks!+M+M+MaBvJqM+M+M+Mrr)rrr)rrr s @rrz4PGDialect.get_unique_constraints..jsN   b+M+M+M+M2e9+M+M+M N N   r)rr/r rGrrr^rrrrrrrr) rr rr rrw UNIQUE_SQLrruniquesrVr s rget_unique_constraintsz PGDialect.get_unique_constraintsIs&&  Frvvl7K7K'   HZ ( ((2B ( C C   qI  6 67788::<< 3 3C"BBuI&)lBvJs{ # #  #MMOO    rc |||||d}d}|tj||}d|iS)Nrrz SELECT pgd.description as table_comment FROM pg_catalog.pg_description pgd WHERE pgd.objsubid = 0 AND pgd.objoid = :table_oid rrG)rr/rr rGr/)rr rr rrw COMMENT_SQLrs rget_table_commentzPGDialect.get_table_commentoso&&  Frvvl7K7K'      sx 44  J J ##rc @|||||d}d}|tj||}g}|D]\} } t jd| t j} | stj d| zd} nGt j d t j d | d } | | d } | r| d rddi| d<| | |S)Nrra SELECT cons.conname as name, pg_get_constraintdef(cons.oid) as src FROM pg_catalog.pg_constraint cons WHERE cons.conrelid = :table_oid AND cons.contype = 'c' rz^CHECK *\((.+)\)( NOT VALID)?$)flagsz)Could not parse CHECK constraint text: %rrz^[\s\n]*\((.+)\)[\s\n]*$z\1r)rrr not_validTrX)rr/rr rGrrDOTALLrrrrrEr)rr rr rrw CHECK_SQLrretrsrcrrrrs rget_check_constraintszPGDialect.get_check_constraintssG&&  Frvvl7K7K'       sx 22i  H H  ID#13biA ) EKLLL*/ry#eQWWQZZ(("g66E ?QWWQZZ ?,7+>'( JJu     rc|p|j}|jsiSd}|dkr|dz }|dz }tj|t jt j}|dkr||}||}g}i}| D]}|d|df} | |vr(|| d  |d >|d|d|d gd x|| <} |d !| d  |d | | |S) Na SELECT t.typname as "name", -- no enum defaults in 8.4 at least -- t.typdefault as "default", pg_catalog.pg_type_is_visible(t.oid) as "visible", n.nspname as "schema", e.enumlabel as "label" FROM pg_catalog.pg_type t LEFT JOIN pg_catalog.pg_namespace n ON n.oid = t.typnamespace LEFT JOIN pg_catalog.pg_enum e ON t.oid = e.enumtypid WHERE t.typtype = 'e' rzAND n.nspname = :schema z ORDER BY "schema", "name", e.oid)rlabelr r rrr0r)rr rr) rrr rGrrr^r\rrr) rr r SQL_ENUMSrrr enum_by_namerrenum_recs rrzPGDialect._load_enumss343( I   S== 3 3I 77 HY   ' '$H,< (   S== F ++A   q ! ! JJLL ' 'D>4<0Cl""S!(+224=AAAA!L"8n#I 00 S!H =,X&--d7m<<< X&&&& rcd}tj|tj}||}i}|D]g}tjd|d d}|dr |df}n|d|df}||d |d d ||<h|S) Na SELECT t.typname as "name", pg_catalog.format_type(t.typbasetype, t.typtypmod) as "attype", not t.typnotnull as "nullable", t.typdefault as "default", pg_catalog.pg_type_is_visible(t.oid) as "visible", n.nspname as "schema" FROM pg_catalog.pg_type t LEFT JOIN pg_catalog.pg_namespace n ON n.oid = t.typnamespace WHERE t.typtype = 'd' rz([^\(]+)rrrrr r.r)rr.r) r rGrrr^rrrrrE) rr  SQL_DOMAINSrrrrrrs rrzPGDialect._load_domainss   H[ ! ! ) )(2B ) C C   q ! !jjll  FY{F8,<==CCAFFF i  9f~'h'8!":.!),GCLL r)NNN)TFrrr)Prrrrsupports_altermax_identifier_lengthsupports_sane_rowcountrsupports_native_booleanr'supports_sequencessequences_optional"preexecute_autoincrement_sequencespostfetch_lastrowidsupports_commentssupports_default_valuessupports_empty_insertsupports_multivalues_insertdefault_paramstylerr-r`statement_compilerr ddl_compilerr~rrrrexecution_ctx_clsr inspectorrr IndexTableconstruct_argumentsreflection_optionsrrWrerr*r4r%r8r2r@rErGrOrRrXrZrbrerhrrsrcacherr~rrrrrrrrrrr#r&r.rrrrs@rrr s DN!")-&"!"&#!MH# L"M#H*IO L %"     L&+" $!!    2<*.'(,% 0000      D    ---===:?4444":? 2 2 2 2--- <<<$$$ $$$$$$$$L$$$$$$$$L % % % %D J J J%%%%N*** * * * * * * * */H****:    NNNN`bbbH0;0;0;0;d &+ kkkkZ 6 6 6HHHT-1# # # # J$$$$$****X2222h$$$$$$$rr)qr collectionsrdatetimerrrrr;r_hstorer_jsonr_rangesr r r renginerrrrrrrsql.ddlrtypesrrrrrrrrrrr rMr!r ImportErrorrrr[UNICODErr%r_DECIMAL_TYPES _FLOAT_TYPES _INT_TYPES LargeBinaryrFloatr TypeEnginerPGInetrPGCidrr PGMacAddrrrrrrNativeForEmulated_AbstractIntervalr PGIntervalrPGBitPGUuidrr6rr4rrp JSONPathTyper-rrrrrrrrStringr SQLCompilerr` DDLCompilerrGenericTypeCompilerr~IdentifierPreparerrrr_CreateDropBaserr DefaultExecutionContextrrrrrrrls hhR$#####  ######)))))))LLL BJ:BD A A BJ@D2: gggiiV% / H (((((x~(((8  8  h!  *****H ***Z(      x"   #####"### #####8=### $$$$$x)8+E$$$N      (     555558 555p      x"   &A8A8A8A8A88 %x}A8A8A8J NFL x M4 M 2 M5:  + fl+ gn+ EJ+ U[ + " + " + +"+w+"+w+ f++++  ho!+" HO#++$ D%+&w'+( U)+* D++, D-+. D/+0 D1+2 33+435+6w7+8 U9+: 3;+<=+>(?+@A+B C+D"9E++F "   U+++ \u u u u u %u u u p r r r r r H(r r r jE E E E E X1E E E P866> > > > > *&> > > B(((((V+(((&&&&&6)&&&92929292928929292xttttt&ttttts4B;;CC