} Z? G d2 d3e? Z@ G d4 d5e? ZAdS )6 ) annotations)contextmanagerN)Any) Awaitable)Callable)Dict)Iterator)List)Mapping)Optional)Sequence)Tuple)Type)
TYPE_CHECKING)TypeVar)Unionconv )batch) schemaobj )util) sqla_compat)formatannotation_fwdref)inspect_formatargspec)inspect_getfullargspec)_literal_bindparam)Literal)Table)
Connection)BinaryExpression) TableClause)
TextClause)Update)Function)Column)Computed)Identity)
SchemaItem)
TypeEngine)BatchOperationsImpl)MigrateOperation) DefaultImpl)MigrationContext)
OperationsBatchOperations_Tc
8 e Zd ZU dZded< ej Z d>d?d
Ze d>d@d Z
e dAd Z e e dBd Z
e ddddd ej d ej df dCd) ZdDd*ZdEd-ZdFd/Z d>dGd5ZdHd7ZdId=ZdS )JAbstractOperationszRBase class for Operations and BatchOperations.
.. versionadded:: 1.11.0
z'Union[DefaultImpl, BatchOperationsImpl]implNmigration_contextr/ Optional[BatchOperationsImpl]returnNonec r || _ |
|j | _ n|| _ t j | | _ dS )zConstruct a new :class:`.Operations`
:param migration_context: a :class:`.MigrationContext`
instance.
N)r6 r5 r
SchemaObjects
schema_obj)selfr6 r5 s i/builddir/build/BUILD/cloudlinux-venv-1.0.12/venv/lib/python3.11/site-packages/alembic/operations/base.py__init__zAbstractOperations.__init__C s; "3 <).DII DI#12CDD namestr
sourcename
Optional[str]Callable[..., Any]c fd}|S )a Register a new operation for this class.
This method is normally used to add new operations
to the :class:`.Operations` class, and possibly the
:class:`.BatchOperations` class as well. All Alembic migration
operations are implemented via this system, however the system
is also available as a public API to facilitate adding custom
operations.
.. seealso::
:ref:`operation_plugins`
c t |
}|j }nt | }|j }t | }|d }|dd ddgk sJ dg|dd< t |dt i}|d rt |d nd}|r|d|z
d }nd}|t
|d z
}t ||d z |d
|d |d t }t j d
d | }t j
d
||||j dz } t t }
|
d| i i } t | |
| t!
|
d j d j d
d|j _ t% |d r|j |
_ | S )Nr r cls
operationsr= formatannotation r c d| z S )N=rL )xs r> zIAbstractOperations.register_operation..register.. s
cAg r@ ) formatvaluerJ z![_]?ForwardRef\(([\'"].+?[\'"])\)c , | d S )Nr )group)ms r> rQ zIAbstractOperations.register_operation..register.. s !''!** r@ z def %(name)s%(args)s:
%(doc)r
return op_cls.%(source_name)s%(apply_kw)s
)rA source_nameargsapply_kwdocop_clsz'This method is proxied on the :class:`.z` class, via the :meth:`..z ` method._legacy_translations)getattr__name__r r r lentupleresubtextwrapdedent__doc__dictglobalsupdateexecsetattr__func__hasattrr\ )rZ fnrV spec name_argsrW num_defaultsdefaulted_valsrX func_textglobals_lclrH rA rC s r> registerz7AbstractOperations.register_operation..registerj s) ! VT** k VZ00 k )"--D QI QqS>e\%::::: $XIacN((? D ,0793tAw<<<L
$!*1|+;+=+=!>!# eDGnn ,N
-DG#QQ - -!8
H 64$$ D ! !#. ( :
I GIIH OOXv . / / /C Hc * * * Cs4y ) ) ) ) <<< ttt5
K
r122
I131HD .Mr@ rL )rH rA rC ru s ``` r> register_operationz%AbstractOperations.register_operationV s7 (H H H H H H H T r@ rZ r c fd}|S )zRegister an implementation for a given :class:`.MigrateOperation`.
This is part of the operation extensibility API.
.. seealso::
:ref:`operation_plugins` - example of use
c N j | | S N)_to_impl dispatch_for)rm rH rZ s r> decoratez7AbstractOperations.implementation_for..decorate s( -CL % %f - -b 1 1 1Ir@ rL )rH rZ r| s `` r> implementation_forz%AbstractOperations.implementation_for s) r@ Iterator[Operations]c # K t | }| |V | d S ry )r0 _install_proxy
_remove_proxy)rH r6 ops r> contextzAbstractOperations.context sI
)
*
*
r@ autorL
table_nameschemarecreate"Literal['auto', 'always', 'never']partial_reorderingOptional[tuple] copy_fromOptional[Table]
table_argsTuple[Any, ...] table_kwargsMapping[str, Any] reflect_argsreflect_kwargsnaming_conventionOptional[Dict[str, str]]Iterator[BatchOperations]c
# K t j | |||||||| |
| } t | j | } | V | dS )a7 Invoke a series of per-table migrations in batch.
Batch mode allows a series of operations specific to a table
to be syntactically grouped together, and allows for alternate
modes of table migration, in particular the "recreate" style of
migration required by SQLite.
"recreate" style is as follows:
1. A new table is created with the new specification, based on the
migration directives within the batch, using a temporary name.
2. the data copied from the existing table to the new table.
3. the existing table is dropped.
4. the new table is renamed to the existing table name.
The directive by default will only use "recreate" style on the
SQLite backend, and only if directives are present which require
this form, e.g. anything other than ``add_column()``. The batch
operation on other backends will proceed using standard ALTER TABLE
operations.
The method is used as a context manager, which returns an instance
of :class:`.BatchOperations`; this object is the same as
:class:`.Operations` except that table names and schema names
are omitted. E.g.::
with op.batch_alter_table("some_table") as batch_op:
batch_op.add_column(Column("foo", Integer))
batch_op.drop_column("bar")
The operations within the context manager are invoked at once
when the context is ended. When run against SQLite, if the
migrations include operations not supported by SQLite's ALTER TABLE,
the entire table will be copied to a new one with the new
specification, moving all data across as well.
The copy operation by default uses reflection to retrieve the current
structure of the table, and therefore :meth:`.batch_alter_table`
in this mode requires that the migration is run in "online" mode.
The ``copy_from`` parameter may be passed which refers to an existing
:class:`.Table` object, which will bypass this reflection step.
.. note:: The table copy operation will currently not copy
CHECK constraints, and may not copy UNIQUE constraints that are
unnamed, as is possible on SQLite. See the section
:ref:`sqlite_batch_constraints` for workarounds.
:param table_name: name of table
:param schema: optional schema name.
:param recreate: under what circumstances the table should be
recreated. At its default of ``"auto"``, the SQLite dialect will
recreate the table if any operations other than ``add_column()``,
``create_index()``, or ``drop_index()`` are
present. Other options include ``"always"`` and ``"never"``.
:param copy_from: optional :class:`~sqlalchemy.schema.Table` object
that will act as the structure of the table being copied. If omitted,
table reflection is used to retrieve the structure of the table.
.. seealso::
:ref:`batch_offline_mode`
:paramref:`~.Operations.batch_alter_table.reflect_args`
:paramref:`~.Operations.batch_alter_table.reflect_kwargs`
:param reflect_args: a sequence of additional positional arguments that
will be applied to the table structure being reflected / copied;
this may be used to pass column and constraint overrides to the
table that will be reflected, in lieu of passing the whole
:class:`~sqlalchemy.schema.Table` using
:paramref:`~.Operations.batch_alter_table.copy_from`.
:param reflect_kwargs: a dictionary of additional keyword arguments
that will be applied to the table structure being copied; this may be
used to pass additional table and reflection options to the table that
will be reflected, in lieu of passing the whole
:class:`~sqlalchemy.schema.Table` using
:paramref:`~.Operations.batch_alter_table.copy_from`.
:param table_args: a sequence of additional positional arguments that
will be applied to the new :class:`~sqlalchemy.schema.Table` when
created, in addition to those copied from the source table.
This may be used to provide additional constraints such as CHECK
constraints that may not be reflected.
:param table_kwargs: a dictionary of additional keyword arguments
that will be applied to the new :class:`~sqlalchemy.schema.Table`
when created, in addition to those copied from the source table.
This may be used to provide for additional table options that may
not be reflected.
:param naming_convention: a naming convention dictionary of the form
described at :ref:`autogen_naming_conventions` which will be applied
to the :class:`~sqlalchemy.schema.MetaData` during the reflection
process. This is typically required if one wants to drop SQLite
constraints, as these constraints will not have names when
reflected on this backend. Requires SQLAlchemy **0.9.4** or greater.
.. seealso::
:ref:`dropping_sqlite_foreign_keys`
:param partial_reordering: a list of tuples, each suggesting a desired
ordering of two or more columns in the newly created table. Requires
that :paramref:`.batch_alter_table.recreate` is set to ``"always"``.
Examples, given a table with columns "a", "b", "c", and "d":
Specify the order of all columns::
with op.batch_alter_table(
"some_table",
recreate="always",
partial_reordering=[("c", "d", "a", "b")],
) as batch_op:
pass
Ensure "d" appears before "c", and "b", appears before "a"::
with op.batch_alter_table(
"some_table",
recreate="always",
partial_reordering=[("d", "c"), ("b", "a")],
) as batch_op:
pass
The ordering of columns not included in the partial_reordering
set is undefined. Therefore it is best to specify the complete
ordering of all columns for best results.
.. versionadded:: 1.4.0
.. note:: batch mode requires SQLAlchemy 0.8 or above.
.. seealso::
:ref:`batch_migrations`
)r5 N)r r, r1 r6 flush)
r= r r r r r r r r r r r5 batch_ops
r> batch_alter_tablez$AbstractOperations.batch_alter_table sm p (
#4#9EEE
r@ c | j S )zWReturn the :class:`.MigrationContext` object that's
currently in use.
)r6 r= s r> get_contextz AbstractOperations.get_context{ s
%%r@ operationr- c n | j || j j j } || | S )zoGiven a :class:`.MigrateOperation`, invoke it in terms of
this :class:`.Operations` instance.
)rz dispatchr6 r5 __dialect__)r= r rm s r> invokezAbstractOperations.invoke s=
]
#
# t-2>
r$ """r@ r c t | S )a Indicate a string name that has already had a naming convention
applied to it.
This feature combines with the SQLAlchemy ``naming_convention`` feature
to disambiguate constraint names that have already had naming
conventions applied to them, versus those that have not. This is
necessary in the case that the ``"%(constraint_name)s"`` token
is used within a naming convention, so that it can be identified
that this particular name should remain fixed.
If the :meth:`.Operations.f` is used on a constraint, the naming
convention will not take effect::
op.add_column("t", "x", Boolean(name=op.f("ck_bool_t_x")))
Above, the CHECK constraint generated will have the name
``ck_bool_t_x`` regardless of whether or not a naming convention is
in use.
Alternatively, if a naming convention is in use, and 'f' is not used,
names will be converted along conventions. If the ``target_metadata``
contains the naming convention
``{"ck": "ck_bool_%(table_name)s_%(constraint_name)s"}``, then the
output of the following:
op.add_column("t", "x", Boolean(name="x"))
will be::
CONSTRAINT ck_bool_t_x CHECK (x in (1, 0)))
The function is rendered in the output of autogenerate when
a particular constraint name is already converted.
r )r= rA s r> fzAbstractOperations.f s H Dzzr@ valueUnion[str, int]type_Optional[TypeEngine[Any]]r c 0 t j d|| S )am Produce an 'inline literal' expression, suitable for
using in an INSERT, UPDATE, or DELETE statement.
When using Alembic in "offline" mode, CRUD operations
aren't compatible with SQLAlchemy's default behavior surrounding
literal values,
which is that they are converted into bound values and passed
separately into the ``execute()`` method of the DBAPI cursor.
An offline SQL
script needs to have these rendered inline. While it should
always be noted that inline literal values are an **enormous**
security hole in an application that handles untrusted input,
a schema migration is not run in this context, so
literals are safe to render inline, with the caveat that
advanced types like dates may not be supported directly
by SQLAlchemy.
See :meth:`.Operations.execute` for an example usage of
:meth:`.Operations.inline_literal`.
The environment can also be configured to attempt to render
"literal" values inline automatically, for those simple types
that are supported by the dialect; see
:paramref:`.EnvironmentContext.configure.literal_binds` for this
more recently added feature.
:param value: The value to render. Strings, integers, and simple
numerics should be supported. Other types like boolean,
dates, etc. may or may not be supported yet by various
backends.
:param type\_: optional - a :class:`sqlalchemy.types.TypeEngine`
subclass stating the type of this value. In SQLAlchemy
expressions, this is usually derived automatically
from the Python type of the value itself, as well as
based on the context in which the value is used.
.. seealso::
:paramref:`.EnvironmentContext.configure.literal_binds`
N)r )r r )r= r r s r> inline_literalz!AbstractOperations.inline_literal s X -dEGGGGr@ r! c $ | j j j S )a Return the current 'bind'.
Under normal circumstances, this is the
:class:`~sqlalchemy.engine.Connection` currently being used
to emit SQL to the database.
In a SQL script context, this value is ``None``. [TODO: verify this]
)r6 r5 bindr s r> get_bindzAbstractOperations.get_bind s %*//r@ async_function Callable[..., Awaitable[_T]]rW kw_argsr2 c $ t j st d | }|t d |j j st
d ddlm} ddl m
} | | } | ||g|R i | S )a Invoke the given asynchronous callable, passing an asynchronous
:class:`~sqlalchemy.ext.asyncio.AsyncConnection` as the first
argument.
This method allows calling async functions from within the
synchronous ``upgrade()`` or ``downgrade()`` alembic migration
method.
The async connection passed to the callable shares the same
transaction as the connection running in the migration context.
Any additional arg or kw_arg passed to this function are passed
to the provided async function.
.. versionadded: 1.11
.. note::
This method can be called only when alembic is called using
an async dialect.
zSQLAlchemy 1.4.18+ requiredNz!Cannot call run_async in SQL modez(Cannot call run_async with a sync enginer )AsyncConnection)
await_only) r
sqla_14_18NotImplementedErrorr dialectis_async
ValueErrorsqlalchemy.ext.asyncior sqlalchemy.utilr _retrieve_proxy_for_target)r= r rW r sync_connr r
async_conns r> run_asyncz AbstractOperations.run_async s 6 % E%&CDD DMMOO %&IJJ J ) I GHH H::::::......$?? JJ
z..FdFFFgFFGGGr@ ry )r6 r/ r5 r7 r8 r9 )rA rB rC rD r8 rE )rZ r r8 rE )r6 r/ r8 r~ )r rB r rD r r r r r r r r r r r r r r r r r8 r )r8 r/ )r r- r8 r )rA rB r8 r )r r r r r8 r )r8 r! )r r rW r r r r8 r2 )r^
__module__ __qualname__re __annotations__r
Dispatcherrz r? classmethodrv r} r r
immutabledictr r r r r r r rL r@ r> r4 r4 9 s 2111 t H
/3E E E E E& 48] ] ] ] []~ [" ^ [ !%7=.2%)&(*<$*<*>*>(*,>D,>,@,@6:f f f f ^fP& & & &# # # #$ $ $ $N JN,H ,H ,H ,H ,H\
0
0
0
0&H &H &H &H &H &Hr@ r4 c 6 e Zd ZdZerddd[d Zdd
d
dddd
dddd
d\d Zd d!d]d(Zddd^d,Zd_d/Z dddddddd0d`d>Z
dd
d?dadDZ dddbdEZ dcdHZ
dddIdddJZdddedLZdddfdMZ dgdddhdNZ dgdddidOZdddjdPZdddIdkdQZddRdldWZdddmdZZdS dS )nr0 a Define high level migration operations.
Each operation corresponds to some schema migration operation,
executed against a particular :class:`.MigrationContext`
which in turn represents connectivity to a database,
or a file output stream.
While :class:`.Operations` is normally configured as
part of the :meth:`.EnvironmentContext.run_migrations`
method called from an ``env.py`` script, a standalone
:class:`.Operations` instance can be
made for use cases external to regular Alembic
migrations by passing in a :class:`.MigrationContext`::
from alembic.migration import MigrationContext
from alembic.operations import Operations
conn = myengine.connect()
ctx = MigrationContext.configure(conn)
op = Operations(ctx)
op.alter_column("t", "c", nullable=True)
Note that as of 0.8, most of the methods on this class are produced
dynamically using the :meth:`.Operations.register_operation`
method.
N)r r rB column Column[Any]r rD r8 r9 c dS )a Issue an "add column" instruction using the current
migration context.
e.g.::
from alembic import op
from sqlalchemy import Column, String
op.add_column("organization", Column("name", String()))
The :meth:`.Operations.add_column` method typically corresponds
to the SQL command "ALTER TABLE... ADD COLUMN". Within the scope
of this command, the column's name, datatype, nullability,
and optional server-generated defaults may be indicated.
.. note::
With the exception of NOT NULL constraints or single-column FOREIGN
KEY constraints, other kinds of constraints such as PRIMARY KEY,
UNIQUE or CHECK constraints **cannot** be generated using this
method; for these constraints, refer to operations such as
:meth:`.Operations.create_primary_key` and
:meth:`.Operations.create_check_constraint`. In particular, the
following :class:`~sqlalchemy.schema.Column` parameters are
**ignored**:
* :paramref:`~sqlalchemy.schema.Column.primary_key` - SQL databases
typically do not support an ALTER operation that can add
individual columns one at a time to an existing primary key
constraint, therefore it's less ambiguous to use the
:meth:`.Operations.create_primary_key` method, which assumes no
existing primary key constraint is present.
* :paramref:`~sqlalchemy.schema.Column.unique` - use the
:meth:`.Operations.create_unique_constraint` method
* :paramref:`~sqlalchemy.schema.Column.index` - use the
:meth:`.Operations.create_index` method
The provided :class:`~sqlalchemy.schema.Column` object may include a
:class:`~sqlalchemy.schema.ForeignKey` constraint directive,
referencing a remote table name. For this specific type of constraint,
Alembic will automatically emit a second ALTER statement in order to
add the single-column FOREIGN KEY constraint separately::
from alembic import op
from sqlalchemy import Column, INTEGER, ForeignKey
op.add_column(
"organization",
Column("account_id", INTEGER, ForeignKey("accounts.id")),
)
The column argument passed to :meth:`.Operations.add_column` is a
:class:`~sqlalchemy.schema.Column` construct, used in the same way it's
used in SQLAlchemy. In particular, values or functions to be indicated
as producing the column's default value on the database side are
specified using the ``server_default`` parameter, and not ``default``
which only specifies Python-side defaults::
from alembic import op
from sqlalchemy import Column, TIMESTAMP, func
# specify "DEFAULT NOW" along with the column add
op.add_column(
"account",
Column("timestamp", TIMESTAMP, server_default=func.now()),
)
:param table_name: String name of the parent table.
:param column: a :class:`sqlalchemy.schema.Column` object
representing the new column.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
NrL )r= r r r s r>
add_columnzOperations.add_column9 s
h
Cr@ F)
nullablecommentserver_defaultnew_column_namer
existing_typeexisting_server_defaultexisting_nullableexisting_commentr column_namer Optional[bool]r Union[str, Literal[False], None]r r r r )Union[TypeEngine, Type[TypeEngine], None]r r *Union[str, bool, Identity, Computed, None]r r kwc
dS )a Issue an "alter column" instruction using the
current migration context.
Generally, only that aspect of the column which
is being changed, i.e. name, type, nullability,
default, needs to be specified. Multiple changes
can also be specified at once and the backend should
"do the right thing", emitting each change either
separately or together as the backend allows.
MySQL has special requirements here, since MySQL
cannot ALTER a column without a full specification.
When producing MySQL-compatible migration files,
it is recommended that the ``existing_type``,
``existing_server_default``, and ``existing_nullable``
parameters be present, if not being altered.
Type changes which are against the SQLAlchemy
"schema" types :class:`~sqlalchemy.types.Boolean`
and :class:`~sqlalchemy.types.Enum` may also
add or drop constraints which accompany those
types on backends that don't support them natively.
The ``existing_type`` argument is
used in this case to identify and remove a previous
constraint that was bound to the type object.
:param table_name: string name of the target table.
:param column_name: string name of the target column,
as it exists before the operation begins.
:param nullable: Optional; specify ``True`` or ``False``
to alter the column's nullability.
:param server_default: Optional; specify a string
SQL expression, :func:`~sqlalchemy.sql.expression.text`,
or :class:`~sqlalchemy.schema.DefaultClause` to indicate
an alteration to the column's default value.
Set to ``None`` to have the default removed.
:param comment: optional string text of a new comment to add to the
column.
.. versionadded:: 1.0.6
:param new_column_name: Optional; specify a string name here to
indicate the new name within a column rename operation.
:param type\_: Optional; a :class:`~sqlalchemy.types.TypeEngine`
type object to specify a change to the column's type.
For SQLAlchemy types that also indicate a constraint (i.e.
:class:`~sqlalchemy.types.Boolean`, :class:`~sqlalchemy.types.Enum`),
the constraint is also generated.
:param autoincrement: set the ``AUTO_INCREMENT`` flag of the column;
currently understood by the MySQL dialect.
:param existing_type: Optional; a
:class:`~sqlalchemy.types.TypeEngine`
type object to specify the previous type. This
is required for all MySQL column alter operations that
don't otherwise specify a new type, as well as for
when nullability is being changed on a SQL Server
column. It is also used if the type is a so-called
SQLlchemy "schema" type which may define a constraint (i.e.
:class:`~sqlalchemy.types.Boolean`,
:class:`~sqlalchemy.types.Enum`),
so that the constraint can be dropped.
:param existing_server_default: Optional; The existing
default value of the column. Required on MySQL if
an existing default is not being changed; else MySQL
removes the default.
:param existing_nullable: Optional; the existing nullability
of the column. Required on MySQL if the existing nullability
is not being changed; else MySQL sets this to NULL.
:param existing_autoincrement: Optional; the existing autoincrement
of the column. Used for MySQL's system of altering a column
that specifies ``AUTO_INCREMENT``.
:param existing_comment: string text of the existing comment on the
column to be maintained. Required on MySQL if the existing comment
on the column is not being changed.
.. versionadded:: 1.0.6
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
:param postgresql_using: String argument which will indicate a
SQL expression to render within the Postgresql-specific USING clause
within ALTER COLUMN. This string is taken directly as raw SQL which
must explicitly include any necessary quoting or escaping of tokens
within the expression.
NrL )r= r r r r r r r r r r r r r s r> alter_columnzOperations.alter_column s
V
Cr@ T) multiinserttableUnion[Table, TableClause]rows
List[dict]r boolc dS )a Issue a "bulk insert" operation using the current
migration context.
This provides a means of representing an INSERT of multiple rows
which works equally well in the context of executing on a live
connection as well as that of generating a SQL script. In the
case of a SQL script, the values are rendered inline into the
statement.
e.g.::
from alembic import op
from datetime import date
from sqlalchemy.sql import table, column
from sqlalchemy import String, Integer, Date
# Create an ad-hoc table to use for the insert statement.
accounts_table = table(
"account",
column("id", Integer),
column("name", String),
column("create_date", Date),
)
op.bulk_insert(
accounts_table,
[
{
"id": 1,
"name": "John Smith",
"create_date": date(2010, 10, 5),
},
{
"id": 2,
"name": "Ed Williams",
"create_date": date(2007, 5, 27),
},
{
"id": 3,
"name": "Wendy Jones",
"create_date": date(2008, 8, 15),
},
],
)
When using --sql mode, some datatypes may not render inline
automatically, such as dates and other special types. When this
issue is present, :meth:`.Operations.inline_literal` may be used::
op.bulk_insert(
accounts_table,
[
{
"id": 1,
"name": "John Smith",
"create_date": op.inline_literal("2010-10-05"),
},
{
"id": 2,
"name": "Ed Williams",
"create_date": op.inline_literal("2007-05-27"),
},
{
"id": 3,
"name": "Wendy Jones",
"create_date": op.inline_literal("2008-08-15"),
},
],
multiinsert=False,
)
When using :meth:`.Operations.inline_literal` in conjunction with
:meth:`.Operations.bulk_insert`, in order for the statement to work
in "online" (e.g. non --sql) mode, the
:paramref:`~.Operations.bulk_insert.multiinsert`
flag should be set to ``False``, which will have the effect of
individual INSERT statements being emitted to the database, each
with a distinct VALUES clause, so that the "inline" values can
still be rendered, rather than attempting to pass the values
as bound parameters.
:param table: a table object which represents the target of the INSERT.
:param rows: a list of dictionaries indicating rows.
:param multiinsert: when at its default of True and --sql mode is not
enabled, the INSERT statement will be executed using
"executemany()" style, where all elements in the list of
dictionaries are passed as bound parameters in a single
list. Setting this to False results in individual INSERT
statements being emitted per parameter set, and is needed
in those cases where non-literal values are present in the
parameter sets.
NrL )r= r r r s r> bulk_insertzOperations.bulk_insert s
L
Cr@ constraint_name condition(Union[str, BinaryExpression, TextClause]c dS )a Issue a "create check constraint" instruction using the
current migration context.
e.g.::
from alembic import op
from sqlalchemy.sql import column, func
op.create_check_constraint(
"ck_user_name_len",
"user",
func.len(column("name")) > 5,
)
CHECK constraints are usually against a SQL expression, so ad-hoc
table metadata is usually needed. The function will convert the given
arguments into a :class:`sqlalchemy.schema.CheckConstraint` bound
to an anonymous table in order to emit the CREATE statement.
:param name: Name of the check constraint. The name is necessary
so that an ALTER statement can be emitted. For setups that
use an automated naming scheme such as that described at
:ref:`sqla:constraint_naming_conventions`,
``name`` here can be ``None``, as the event listener will
apply the name to the constraint object when it is associated
with the table.
:param table_name: String name of the source table.
:param condition: SQL expression that's the condition of the
constraint. Can be a string or SQLAlchemy expression language
structure.
:param deferrable: optional bool. If set, emit DEFERRABLE or
NOT DEFERRABLE when issuing DDL for this constraint.
:param initially: optional string. If set, emit INITIALLY
when issuing DDL for this constraint.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
NrL )r= r r r r r s r> create_check_constraintz"Operations.create_check_constraintd s
b
Cr@ elementsr c dS )a@ Issue an alter to create an EXCLUDE constraint using the
current migration context.
.. note:: This method is Postgresql specific, and additionally
requires at least SQLAlchemy 1.0.
e.g.::
from alembic import op
op.create_exclude_constraint(
"user_excl",
"user",
("period", "&&"),
("group", "="),
where=("group != 'some group'"),
)
Note that the expressions work the same way as that of
the ``ExcludeConstraint`` object itself; if plain strings are
passed, quoting rules must be applied manually.
:param name: Name of the constraint.
:param table_name: String name of the source table.
:param elements: exclude conditions.
:param where: SQL expression or SQL string with optional WHERE
clause.
:param deferrable: optional bool. If set, emit DEFERRABLE or
NOT DEFERRABLE when issuing DDL for this constraint.
:param initially: optional string. If set, emit INITIALLY
when issuing DDL for this constraint.
:param schema: Optional schema name to operate within.
NrL )r= r r r r s r> create_exclude_constraintz$Operations.create_exclude_constraint s
R
Cr@ )onupdateondelete
deferrable initiallymatch
source_schemareferent_schema source_tablereferent_table
local_cols List[str] remote_colsr r r r r r r
dialect_kwc dS )a^ Issue a "create foreign key" instruction using the
current migration context.
e.g.::
from alembic import op
op.create_foreign_key(
"fk_user_address",
"address",
"user",
["user_id"],
["id"],
)
This internally generates a :class:`~sqlalchemy.schema.Table` object
containing the necessary columns, then generates a new
:class:`~sqlalchemy.schema.ForeignKeyConstraint`
object which it then associates with the
:class:`~sqlalchemy.schema.Table`.
Any event listeners associated with this action will be fired
off normally. The :class:`~sqlalchemy.schema.AddConstraint`
construct is ultimately used to generate the ALTER statement.
:param constraint_name: Name of the foreign key constraint. The name
is necessary so that an ALTER statement can be emitted. For setups
that use an automated naming scheme such as that described at
:ref:`sqla:constraint_naming_conventions`,
``name`` here can be ``None``, as the event listener will
apply the name to the constraint object when it is associated
with the table.
:param source_table: String name of the source table.
:param referent_table: String name of the destination table.
:param local_cols: a list of string column names in the
source table.
:param remote_cols: a list of string column names in the
remote table.
:param onupdate: Optional string. If set, emit ON UPDATE when
issuing DDL for this constraint. Typical values include CASCADE,
DELETE and RESTRICT.
:param ondelete: Optional string. If set, emit ON DELETE when
issuing DDL for this constraint. Typical values include CASCADE,
DELETE and RESTRICT.
:param deferrable: optional bool. If set, emit DEFERRABLE or NOT
DEFERRABLE when issuing DDL for this constraint.
:param source_schema: Optional schema name of the source table.
:param referent_schema: Optional schema name of the destination table.
NrL )r= r r r r r r r r r r r r r s r> create_foreign_keyz Operations.create_foreign_key s
D
Cr@ )r unique
index_namecolumns/Sequence[Union[str, TextClause, Function[Any]]]r c dS )a Issue a "create index" instruction using the current
migration context.
e.g.::
from alembic import op
op.create_index("ik_test", "t1", ["foo", "bar"])
Functional indexes can be produced by using the
:func:`sqlalchemy.sql.expression.text` construct::
from alembic import op
from sqlalchemy import text
op.create_index("ik_test", "t1", [text("lower(foo)")])
:param index_name: name of the index.
:param table_name: name of the owning table.
:param columns: a list consisting of string column names and/or
:func:`~sqlalchemy.sql.expression.text` constructs.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
:param unique: If True, create a unique index.
:param quote:
Force quoting of this column's name on or off, corresponding
to ``True`` or ``False``. When left at its default
of ``None``, the column identifier will be quoted according to
whether the name is case sensitive (identifiers with at least one
upper case character are treated as case sensitive), or if it's a
reserved word. This flag is only needed to force quoting of a
reserved word which is not known by the SQLAlchemy dialect.
:param \**kw: Additional keyword arguments not mentioned above are
dialect specific, and passed in the form
``_``.
See the documentation regarding an individual dialect at
:ref:`dialect_toplevel` for detail on documented arguments.
NrL )r= r r r r r r s r> create_indexzOperations.create_index s
j
Cr@ c dS )a Issue a "create primary key" instruction using the current
migration context.
e.g.::
from alembic import op
op.create_primary_key("pk_my_table", "my_table", ["id", "version"])
This internally generates a :class:`~sqlalchemy.schema.Table` object
containing the necessary columns, then generates a new
:class:`~sqlalchemy.schema.PrimaryKeyConstraint`
object which it then associates with the
:class:`~sqlalchemy.schema.Table`.
Any event listeners associated with this action will be fired
off normally. The :class:`~sqlalchemy.schema.AddConstraint`
construct is ultimately used to generate the ALTER statement.
:param constraint_name: Name of the primary key constraint. The name
is necessary so that an ALTER statement can be emitted. For setups
that use an automated naming scheme such as that described at
:ref:`sqla:constraint_naming_conventions`
``name`` here can be ``None``, as the event listener will
apply the name to the constraint object when it is associated
with the table.
:param table_name: String name of the target table.
:param columns: a list of string column names to be applied to the
primary key constraint.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
NrL )r= r r r r s r> create_primary_keyz Operations.create_primary_key= s
T
Cr@ r* r c dS )aI
Issue a "create table" instruction using the current migration
context.
This directive receives an argument list similar to that of the
traditional :class:`sqlalchemy.schema.Table` construct, but without the
metadata::
from sqlalchemy import INTEGER, VARCHAR, NVARCHAR, Column
from alembic import op
op.create_table(
"account",
Column("id", INTEGER, primary_key=True),
Column("name", VARCHAR(50), nullable=False),
Column("description", NVARCHAR(200)),
Column("timestamp", TIMESTAMP, server_default=func.now()),
)
Note that :meth:`.create_table` accepts
:class:`~sqlalchemy.schema.Column`
constructs directly from the SQLAlchemy library. In particular,
default values to be created on the database side are
specified using the ``server_default`` parameter, and not
``default`` which only specifies Python-side defaults::
from alembic import op
from sqlalchemy import Column, TIMESTAMP, func
# specify "DEFAULT NOW" along with the "timestamp" column
op.create_table(
"account",
Column("id", INTEGER, primary_key=True),
Column("timestamp", TIMESTAMP, server_default=func.now()),
)
The function also returns a newly created
:class:`~sqlalchemy.schema.Table` object, corresponding to the table
specification given, which is suitable for
immediate SQL operations, in particular
:meth:`.Operations.bulk_insert`::
from sqlalchemy import INTEGER, VARCHAR, NVARCHAR, Column
from alembic import op
account_table = op.create_table(
"account",
Column("id", INTEGER, primary_key=True),
Column("name", VARCHAR(50), nullable=False),
Column("description", NVARCHAR(200)),
Column("timestamp", TIMESTAMP, server_default=func.now()),
)
op.bulk_insert(
account_table,
[
{"name": "A1", "description": "account 1"},
{"name": "A2", "description": "account 2"},
],
)
:param table_name: Name of the table
:param \*columns: collection of :class:`~sqlalchemy.schema.Column`
objects within
the table, as well as optional :class:`~sqlalchemy.schema.Constraint`
objects
and :class:`~.sqlalchemy.schema.Index` objects.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
:param \**kw: Other keyword arguments are passed to the underlying
:class:`sqlalchemy.schema.Table` object created for the command.
:return: the :class:`~sqlalchemy.schema.Table` object corresponding
to the parameters given.
NrL )r= r r r s r> create_tablezOperations.create_tablei s
`
Cr@ )r r c dS )a Emit a COMMENT ON operation to set the comment for a table.
.. versionadded:: 1.0.6
:param table_name: string name of the target table.
:param comment: string value of the comment being registered against
the specified table.
:param existing_comment: String value of a comment
already registered on the specified table, used within autogenerate
so that the operation is reversible, but not required for direct
use.
.. seealso::
:meth:`.Operations.drop_table_comment`
:paramref:`.Operations.alter_column.comment`
NrL )r= r r r r s r> create_table_commentz Operations.create_table_comment s 6
Cr@
Sequence[str]c dS )an Issue a "create unique constraint" instruction using the
current migration context.
e.g.::
from alembic import op
op.create_unique_constraint("uq_user_name", "user", ["name"])
This internally generates a :class:`~sqlalchemy.schema.Table` object
containing the necessary columns, then generates a new
:class:`~sqlalchemy.schema.UniqueConstraint`
object which it then associates with the
:class:`~sqlalchemy.schema.Table`.
Any event listeners associated with this action will be fired
off normally. The :class:`~sqlalchemy.schema.AddConstraint`
construct is ultimately used to generate the ALTER statement.
:param name: Name of the unique constraint. The name is necessary
so that an ALTER statement can be emitted. For setups that
use an automated naming scheme such as that described at
:ref:`sqla:constraint_naming_conventions`,
``name`` here can be ``None``, as the event listener will
apply the name to the constraint object when it is associated
with the table.
:param table_name: String name of the source table.
:param columns: a list of string column names in the
source table.
:param deferrable: optional bool. If set, emit DEFERRABLE or
NOT DEFERRABLE when issuing DDL for this constraint.
:param initially: optional string. If set, emit INITIALLY
when issuing DDL for this constraint.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
NrL )r= r r r r r s r> create_unique_constraintz#Operations.create_unique_constraint s
\
Cr@ c dS )a Issue a "drop column" instruction using the current
migration context.
e.g.::
drop_column("organization", "account_id")
:param table_name: name of table
:param column_name: name of column
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
:param mssql_drop_check: Optional boolean. When ``True``, on
Microsoft SQL Server only, first
drop the CHECK constraint on the column using a
SQL-script-compatible
block that selects into a @variable from sys.check_constraints,
then exec's a separate DROP CONSTRAINT for that constraint.
:param mssql_drop_default: Optional boolean. When ``True``, on
Microsoft SQL Server only, first
drop the DEFAULT constraint on the column using a
SQL-script-compatible
block that selects into a @variable from sys.default_constraints,
then exec's a separate DROP CONSTRAINT for that default.
:param mssql_drop_foreign_key: Optional boolean. When ``True``, on
Microsoft SQL Server only, first
drop a single FOREIGN KEY constraint on the column using a
SQL-script-compatible
block that selects into a @variable from
sys.foreign_keys/sys.foreign_key_columns,
then exec's a separate DROP CONSTRAINT for that default. Only
works if the column has exactly one FK constraint which refers to
it, at the moment.
NrL )r= r r r r s r> drop_columnzOperations.drop_column s
X
Cr@ c dS )a. Drop a constraint of the given name, typically via DROP CONSTRAINT.
:param constraint_name: name of the constraint.
:param table_name: table name.
:param type\_: optional, required on MySQL. can be
'foreignkey', 'primary', 'unique', or 'check'.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
NrL )r= r r r r s r> drop_constraintzOperations.drop_constraint6 (
Cr@ c dS )a Issue a "drop index" instruction using the current
migration context.
e.g.::
drop_index("accounts")
:param index_name: name of the index.
:param table_name: name of the owning table. Some
backends such as Microsoft SQL Server require this.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
:param \**kw: Additional keyword arguments not mentioned above are
dialect specific, and passed in the form
``_``.
See the documentation regarding an individual dialect at
:ref:`dialect_toplevel` for detail on documented arguments.
NrL )r= r r r r s r>
drop_indexzOperations.drop_indexL s :
Cr@ c dS )ad Issue a "drop table" instruction using the current
migration context.
e.g.::
drop_table("accounts")
:param table_name: Name of the table
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
:param \**kw: Other keyword arguments are passed to the underlying
:class:`sqlalchemy.schema.Table` object created for the command.
NrL )r= r r r s r>
drop_tablezOperations.drop_tablek r r@ c dS )a Issue a "drop table comment" operation to
remove an existing comment set on a table.
.. versionadded:: 1.0.6
:param table_name: string name of the target table.
:param existing_comment: An optional string value of a comment already
registered on the specified table.
.. seealso::
:meth:`.Operations.create_table_comment`
:paramref:`.Operations.alter_column.comment`
NrL )r= r r r s r> drop_table_commentz Operations.drop_table_comment s .
Cr@ execution_optionssqltext Union[str, TextClause, Update]r Optional[dict[str, Any]]c dS )a Execute the given SQL using the current migration context.
The given SQL can be a plain string, e.g.::
op.execute("INSERT INTO table (foo) VALUES ('some value')")
Or it can be any kind of Core SQL Expression construct, such as
below where we use an update construct::
from sqlalchemy.sql import table, column
from sqlalchemy import String
from alembic import op
account = table("account", column("name", String))
op.execute(
account.update()
.where(account.c.name == op.inline_literal("account 1"))
.values({"name": op.inline_literal("account 2")})
)
Above, we made use of the SQLAlchemy
:func:`sqlalchemy.sql.expression.table` and
:func:`sqlalchemy.sql.expression.column` constructs to make a brief,
ad-hoc table construct just for our UPDATE statement. A full
:class:`~sqlalchemy.schema.Table` construct of course works perfectly
fine as well, though note it's a recommended practice to at least
ensure the definition of a table is self-contained within the migration
script, rather than imported from a module that may break compatibility
with older migrations.
In a SQL script context, the statement is emitted directly to the
output stream. There is *no* return result, however, as this
function is oriented towards generating a change script
that can run in "offline" mode. Additionally, parameterized
statements are discouraged here, as they *will not work* in offline
mode. Above, we use :meth:`.inline_literal` where parameters are
to be used.
For full interaction with a connected database where parameters can
also be used normally, use the "bind" available from the context::
from alembic import op
connection = op.get_bind()
connection.execute(
account.update()
.where(account.c.name == "account 1")
.values({"name": "account 2"})
)
Additionally, when passing the statement as a plain string, it is first
coerceed into a :func:`sqlalchemy.sql.expression.text` construct
before being passed along. In the less likely case that the
literal SQL string contains a colon, it must be escaped with a
backslash, as::
op.execute(r"INSERT INTO table (foo) VALUES ('\:colon_value')")
:param sqltext: Any legal SQLAlchemy expression, including:
* a string
* a :func:`sqlalchemy.sql.expression.text` construct.
* a :func:`sqlalchemy.sql.expression.insert` construct.
* a :func:`sqlalchemy.sql.expression.update`,
:func:`sqlalchemy.sql.expression.insert`,
or :func:`sqlalchemy.sql.expression.delete` construct.
* Any "executable" described in SQLAlchemy Core documentation,
noting that no result set is returned.
.. note:: when passing a plain string, the statement is coerced into
a :func:`sqlalchemy.sql.expression.text` construct. This construct
considers symbols with colons, e.g. ``:foo`` to be bound parameters.
To avoid this, ensure that colon symbols are escaped, e.g.
``\:foo``.
:param execution_options: Optional dictionary of
execution options, will be passed to
:meth:`sqlalchemy.engine.Connection.execution_options`.
NrL r= r r s r> executezOperations.execute s
n
Cr@ old_table_namenew_table_namec dS )a Emit an ALTER TABLE to rename a table.
:param old_table_name: old name.
:param new_table_name: new name.
:param schema: Optional schema name to operate within. To control
quoting of the schema outside of the default behavior, use
the SQLAlchemy construct
:class:`~sqlalchemy.sql.elements.quoted_name`.
NrL )r= r r r s r> rename_tablezOperations.rename_table "
Cr@ )r rB r r r rD r8 r9 ) r rB r rB r r r r r r r rD r r r r r r r r r rD r rD r r r8 r9 )r r r r r r r8 r9 ) r rD r rB r r r rD r r r8 r9 )
r rB r rB r r r r r8 r ) r rD r rB r rB r r r r r rD r rD r r r rD r rD r rD r rD r r r8 r9 )r rD r rB r r r rD r r r r r8 r9 )
r rD r rB r r r rD r8 r9 )r rB r r* r r r8 r )
r rB r rD r rD r rD r8 r9 ) r rD r rB r r r rD r r r8 r )
r rB r rB r rD r r r8 r9 ry )
r rB r rB r rD r rD r8 r9 )
r rB r rD r rD r r r8 r9 )r rB r rD r r r8 r9 )r rB r rD r rD r8 r9 r r r r r8 r9 )r rB r rB r rD r8 r9 )r^ r r re r r r r r r r r r r r r r r
r
r r r r rL r@ r> r0 r0 s : P %) T T T T T T v (,8="'-1?CGK 04.2$(!k k k k k k d !% f f f f f f \ %)
1 1 1 1 1 1 f) ) ) ) f '+&*)-'+#'+/-1 B B B B B B T %) 5 5 5 5 5 5 z %)
* * * * * * XP P P P n /3$(
F %)
. . . . . . j %) , , , , , , d $( %)
2 )-
%) @ ?C 4 /3$( : ;? W W W W W W | %) P Pr@ r0 c e Zd ZU dZded< d Zer^ddddHdZdddddddddddd dId"ZdJd&Z dKd(Z
ddddddd)dLd5Z dMd8Z dNd9Z
dd:dOd;ZdPd=ZdQd>Z dRdSd?ZdTd@Zdd:dUdAZddBdVdGZdS dS )Wr1 a Modifies the interface :class:`.Operations` for batch mode.
This basically omits the ``table_name`` and ``schema`` parameters
from associated methods, as these are a given when running under batch
mode.
.. seealso::
:meth:`.Operations.batch_alter_table`
Note that as of 0.8, most of the methods on this class are produced
dynamically using the :meth:`.Operations.register_operation`
method.
r, r5 c & t d|z )Nz>The %s method does not apply to a batch table alter operation.)r )r= r s r> _noopzBatchOperations._noop s ! L
r@ N)
insert_before insert_afterr r r# rD r$ r8 r9 c dS )zIssue an "add column" instruction using the current
batch migration context.
.. seealso::
:meth:`.Operations.add_column`
NrL )r= r r# r$ s r> r zBatchOperations.add_column' s
Cr@ F) r r r r r r r r r r# r$ r rB r r r r r r r r r r r r r r r c dS )a Issue an "alter column" instruction using the current
batch migration context.
Parameters are the same as that of :meth:`.Operations.alter_column`,
as well as the following option(s):
:param insert_before: String name of an existing column which this
column should be placed before, when creating the new table.
.. versionadded:: 1.4.0
:param insert_after: String name of an existing column which this
column should be placed after, when creating the new table. If
both :paramref:`.BatchOperations.alter_column.insert_before`
and :paramref:`.BatchOperations.alter_column.insert_after` are
omitted, the column is inserted after the last existing column
in the table.
.. versionadded:: 1.4.0
.. seealso::
:meth:`.Operations.alter_column`
NrL )r= r r r r r r r r r r r# r$ r s r> r z BatchOperations.alter_column8 s
Z
Cr@ r r r c dS )a; Issue a "create check constraint" instruction using the
current batch migration context.
The batch form of this call omits the ``source`` and ``schema``
arguments from the call.
.. seealso::
:meth:`.Operations.create_check_constraint`
NrL )r= r r r s r> r z'BatchOperations.create_check_constraintg r r@ r c dS )aK Issue a "create exclude constraint" instruction using the
current batch migration context.
.. note:: This method is Postgresql specific, and additionally
requires at least SQLAlchemy 1.0.
.. seealso::
:meth:`.Operations.create_exclude_constraint`
NrL )r= r r r s r> r z)BatchOperations.create_exclude_constraintz
Cr@ )r r r r r r r r r r r r r r r r r c dS )ac Issue a "create foreign key" instruction using the
current batch migration context.
The batch form of this call omits the ``source`` and ``source_schema``
arguments from the call.
e.g.::
with batch_alter_table("address") as batch_op:
batch_op.create_foreign_key(
"fk_user_address",
"user",
["user_id"],
["id"],
)
.. seealso::
:meth:`.Operations.create_foreign_key`
NrL ) r= r r r r r r r r r r r s r> r z"BatchOperations.create_foreign_key s
H
Cr@ r r c dS )zIssue a "create index" instruction using the
current batch migration context.
.. seealso::
:meth:`.Operations.create_index`
NrL )r= r r r s r> r z BatchOperations.create_index s
Cr@ c dS )a5 Issue a "create primary key" instruction using the
current batch migration context.
The batch form of this call omits the ``table_name`` and ``schema``
arguments from the call.
.. seealso::
:meth:`.Operations.create_primary_key`
NrL )r= r r s r> r z"BatchOperations.create_primary_key r) r@ )r c dS )a Emit a COMMENT ON operation to set the comment for a table
using the current batch migration context.
.. versionadded:: 1.6.0
:param comment: string value of the comment being registered against
the specified table.
:param existing_comment: String value of a comment
already registered on the specified table, used within autogenerate
so that the operation is reversible, but not required for direct
use.
NrL )r= r r s r> r z$BatchOperations.create_table_comment s &
Cr@ r c dS )a= Issue a "create unique constraint" instruction using the
current batch migration context.
The batch form of this call omits the ``source`` and ``schema``
arguments from the call.
.. seealso::
:meth:`.Operations.create_unique_constraint`
NrL )r= r r r s r> r z(BatchOperations.create_unique_constraint r) r@ c dS )zIssue a "drop column" instruction using the current
batch migration context.
.. seealso::
:meth:`.Operations.drop_column`
NrL )r= r r s r> r zBatchOperations.drop_column
Cr@ c dS )a/ Issue a "drop constraint" instruction using the
current batch migration context.
The batch form of this call omits the ``table_name`` and ``schema``
arguments from the call.
.. seealso::
:meth:`.Operations.drop_constraint`
NrL )r= r r s r> r
z BatchOperations.drop_constraint r) r@ c dS )zIssue a "drop index" instruction using the
current batch migration context.
.. seealso::
:meth:`.Operations.drop_index`
NrL )r= r r s r> r
zBatchOperations.drop_index
r0 r@ c dS )aN Issue a "drop table comment" operation to
remove an existing comment set on a table using the current
batch operations context.
.. versionadded:: 1.6.0
:param existing_comment: An optional string value of a comment already
registered on the specified table.
NrL )r= r s r> r z"BatchOperations.drop_table_comment
Cr@ r r r r r c dS )zExecute the given SQL using the current migration context.
.. seealso::
:meth:`.Operations.execute`
NrL r s r> r zBatchOperations.execute' r4 r@ )r r r# rD r$ rD r8 r9 ) r rB r r r r r r r rD r r r r r r r r r rD r# rD r$ rD r r r8 r9 )r rB r r r r r8 r9 )r rB r r r r )r rB r rB r r r r r rD r rD r rD r r r rD r rD r r r8 r9 )r rB r r r r r8 r9 )r rB r r r8 r9 )r rD r rD r8 r9 )r rB r r r r r8 r )r rB r r r8 r9 ry )r rB r rD r8 r9 )r rB r r r8 r9 )r rD r8 r9 r )r^ r r re r r" r r r r r r r r r r r r
r
r r rL r@ r> r1 r1 s
R ,0*. * (,8="'-1?CGK 04.2+/*.!- - - - - - ^ & . .2&*&*)-'+#'$ $ $ $ $ $ L ( /3 * @D 8<
& ;?
KR Rr@ r1 )B
__future__r
contextlibr ra rc typingr r r r r r
r r r
r r r r r sqlalchemy.sql.elementsr r r r r util.compatr r r util.sqla_compatr r
sqlalchemyr sqlalchemy.enginer! sqlalchemy.sql.expressionr" r# r$ r% sqlalchemy.sql.functionsr& sqlalchemy.sql.schemar' r( r) r* sqlalchemy.typesr+ r, opsr- ddlr. runtime.migrationr/ __all__r2 ModuleClsProxyr4 r0 r1 rL r@ r> rH s " " " " " " % % % % % % ( ( ( ( ( ( 1 1 1 1 1 1 / / / / / / 0 0 0 0 0 0 1 1 1 1 1 1 5 ,,,,,,::::::555555444444000000111111,,,,,,............000000++++++******%%%%%%!!!!!!444444
+ WT]]ZH ZH ZH ZH ZH, ZH ZH ZHzn n n n n# n n nf k k k k k( k k k k kr@