관리-도구
편집 파일: ops.cpython-37.opt-1.pyc
B �M!V� � @ s� d dl mZ d dlmZ ddl mZ ddlmZ ddlmZmZ ddl Z G d d � d e �Z G d d � d e �Z e� d �e� d d�G dd� de ���Ze� d�e� dd�G dd� de ���Ze� d�e� dd�G dd� de ���Ze� d�e� dd�G dd � d e ���Ze� d �e� d d �G d d � d e ���Ze� d!�e� d!d"�G d#d$� d$e ���Ze� d%�e� d%d&�G d'd(� d(e ���Ze� d)�G d*d+� d+e ��Ze� d,�G d-d.� d.e ��ZG d/d0� d0e �Ze� d1�G d2d3� d3e��Ze� d4�e� d4d5�G d6d7� d7e���Ze� d8�e� d8d9�G d:d;� d;e���Ze� d<�e� d<d=�G d>d?� d?e���Ze� d@�G dAdB� dBe ��Z e� dC�G dDdE� dEe ��Z G dFdG� dGe �Z G dHdI� dIe �Z G dJdK� dKe �Z G dLdM� dMe �Z!G dNdO� dOe �Z"dS )P� )�util)� sqla_compat� )� schemaobj� )�NULLTYPE)� Operations�BatchOperationsNc @ s e Zd ZdZejdd� �ZdS )�MigrateOperationa base class for migration command and organization objects. This system is part of the operation extensibility API. .. versionadded:: 0.8.0 .. seealso:: :ref:`operation_objects` :ref:`operation_plugins` :ref:`customizing_revision` c C s i S )z�A dictionary that may be used to store arbitrary information along with this :class:`.MigrateOperation` object. � )�selfr r �G/opt/alt/python37/lib/python3.7/site-packages/alembic/operations/ops.py�info s zMigrateOperation.infoN)�__name__� __module__� __qualname__�__doc__r Zmemoized_propertyr r r r r r s r c @ s8 e Zd ZdZedd� �Zedd� �Zdd� Zdd � Z d S ) �AddConstraintOpz&Represent an add constraint operation.c C s t � �d S )N)�NotImplementedError)r r r r �constraint_type& s z AddConstraintOp.constraint_typec C s( t jtjtjtjtjd�}||j |�S )N)�unique_constraint�foreign_key_constraint�primary_key_constraint�check_constraint�column_check_constraint)�CreateUniqueConstraintOp�from_constraint�CreateForeignKeyOp�CreatePrimaryKeyOp�CreateCheckConstraintOp�__visit_name__)�cls� constraintZfuncsr r r r * s z AddConstraintOp.from_constraintc C s t �| �� �S )N)�DropConstraintOpr � to_constraint)r r r r �reverse5 s zAddConstraintOp.reversec C s d| � � fS )NZadd_constraint)r$ )r r r r � to_diff_tuple8 s z AddConstraintOp.to_diff_tupleN) r r r r �propertyr � classmethodr r% r& r r r r r # s r �drop_constraint�batch_drop_constraintc @ sh e Zd ZdZddd�Zdd� Zdd� Zed d � �Zd d � Z ee � d dg�ddd���Z eddd��Z dS )r# z&Represent a drop constraint operation.Nc C s" || _ || _|| _|| _|| _d S )N)�constraint_name� table_namer �schema�_orig_constraint)r r+ r, �type_r- r. r r r �__init__A s zDropConstraintOp.__init__c C s | j d krtd��t�| j �S )Nz?operation is not reversible; original constraint is not present)r. � ValueErrorr r )r r r r r% K s zDropConstraintOp.reversec C s& | j dkrd| �� fS d| �� fS d S )N� foreignkeyZ remove_fkZremove_constraint)r r$ )r r r r r& R s z DropConstraintOp.to_diff_tuplec C s8 dddddd�}t �|�}| |j|j|j||j |d�S )N�uniquer2 Zprimary�check)r r r r r )r- r/ r. )r �_table_for_constraint�namer- r )r! r" �types�constraint_tabler r r r X s z DropConstraintOp.from_constraintc C s | j d k r| j S td��d S )NzAconstraint cannot be produced; original constraint is not present)r. r1 )r r r r r$ k s z DropConstraintOp.to_constraint)�typer/ )r6 r+ c C s | ||||d�}|� |�S )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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name )r/ r- )�invoke)r! � operationsr+ r, r/ r- �opr r r r) s s z DropConstraintOp.drop_constraintc C s" | ||j j||j jd�}|�|�S )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` .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name )r/ r- )�implr, r- r: )r! r; r+ r/ r< r r r r* � s z&DropConstraintOp.batch_drop_constraint)NNN)NN)N)r r r r r0 r% r& r( r r$ r �_with_legacy_namesr) r* r r r r r# < s r# �create_primary_key�batch_create_primary_keyc @ s\ e Zd ZdZdZddd�Zedd� �Zddd �Zee � d d g�dd d ���Z edd� �Z dS )r z)Represent a create primary key operation.Z primarykeyNc K s( || _ || _|| _|| _|| _|| _d S )N)r+ r, �columnsr- r. �kw)r r+ r, rA r- r. rB r r r r0 � s zCreatePrimaryKeyOp.__init__c C s$ t �|�}| |j|j|j|j|d�S )N)r- r. )r r5 r6 rA r- )r! r" r8 r r r r � s z"CreatePrimaryKeyOp.from_constraintc C s4 | j d k r| j S t�|�}|j| j| j| j| jd�S )N)r- )r. r � SchemaObjectsr r+ r, rA r- )r �migration_context� schema_objr r r r$ � s z CreatePrimaryKeyOp.to_constraint)r6 r+ )ZcolsrA c C s | ||||�}|� |�S )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 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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name * cols -> columns )r: )r! r; r+ r, rA r- r< r r r r? � s 5z%CreatePrimaryKeyOp.create_primary_keyc C s" | ||j j||j jd�}|�|�S )a 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` )r- )r= r, r- r: )r! r; r+ rA r< r r r r@ s z+CreatePrimaryKeyOp.batch_create_primary_key)NN)N)N) r r r r r r0 r( r r$ r r> r? r@ r r r r r � s 1r �create_unique_constraint� batch_create_unique_constraintc @ sj e Zd ZdZdZddd�Zedd� �Zddd �Zee � d d d g�dd d���Z ee � d g�dd� ��Z dS )r z/Represent a create unique constraint operation.r3 Nc K s( || _ || _|| _|| _|| _|| _d S )N)r+ r, rA r- r. rB )r r+ r, rA r- r. rB r r r r0 ' s z!CreateUniqueConstraintOp.__init__c C sZ t �|�}i }|jr |j|d< |jr.|j|d< | |j|jdd� |jD �f|j|d�|��S )N� deferrable� initiallyc S s g | ] }|j �qS r )r6 )�.0�cr r r � <listcomp>> s z<CreateUniqueConstraintOp.from_constraint.<locals>.<listcomp>)r- r. )r r5 rH rI r6 rA r- )r! r" r8 rB r r r r 1 s z(CreateUniqueConstraintOp.from_constraintc C s> | j d k r| j S t�|�}|j| j| j| jfd| ji| j��S )Nr- ) r. r rC r r+ r, rA r- rB )r rD rE r r r r$ D s z&CreateUniqueConstraintOp.to_constraint)r6 r+ )�sourcer, )� local_colsrA c K s" | |||fd|i|��}|� |�S )aG 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 <value> 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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name * source -> table_name * local_cols -> columns r- )r: )r! r; r+ r, rA r- rB r< r r r rF M s 9 z1CreateUniqueConstraintOp.create_unique_constraintc K s* |j j|d< | ||j j|f|�}|�|�S )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` .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name r- )r= r- r, r: )r! r; r+ rA rB r< r r r rG � s z7CreateUniqueConstraintOp.batch_create_unique_constraint)NN)N)N) r r r r r r0 r( r r$ r r> rF rG r r r r r s 7r �create_foreign_key�batch_create_foreign_keyc @ sv e Zd ZdZdZddd�Zdd� Zedd � �Zdd d �Z ee � d d dg�ddd���Z ee � d dg�ddd���Z dS )r z4Represent a create foreign key constraint operation.r2 Nc K s. || _ || _|| _|| _|| _|| _|| _d S )N)r+ � source_table�referent_tablerN � remote_colsr. rB )r r+ rQ rR rN rS r. rB r r r r0 � s zCreateForeignKeyOp.__init__c C s d| � � fS )NZadd_fk)r$ )r r r r r& � s z CreateForeignKeyOp.to_diff_tuplec C s� i }|j r|j |d< |jr$|j|d< |jr4|j|d< |jrD|j|d< |jrT|j|d< t�|�\ }}}}}}} } } } ||d< ||d< | |j||||fd|i|��S ) N�onupdate�ondeleterI rH � use_alter� source_schema�referent_schemar. )rT rU rI rH rV r Z_fk_specr6 ) r! r" rB rW rQ Zsource_columnsZ target_schemaZ target_tableZtarget_columnsrT rU rH rI r r r r � s, z"CreateForeignKeyOp.from_constraintc C s< | j d k r| j S t�|�}|j| j| j| j| j| jf| j �S )N) r. r rC r r+ rQ rR rN rS rB )r rD rE r r r r$ � s z CreateForeignKeyOp.to_constraint)r6 r+ )rM rQ )ZreferentrR c K s2 | |||||f||| | | | | d�|��}|� |�S )aW 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 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 <value> when issuing DDL for this constraint. Typical values include CASCADE, DELETE and RESTRICT. :param ondelete: Optional string. If set, emit ON DELETE <value> 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. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name * source -> source_table * referent -> referent_table )rT rU rH rW rX rI �match)r: )r! r; r+ rQ rR rN rS rT rU rH rI rY rW rX � dialect_kwr< r r r rO � s @z%CreateForeignKeyOp.create_foreign_keyc K s: | ||j j|||f||| |j j|| | d�| ��} |�| �S )a� 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` .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name * referent -> referent_table )rT rU rH rW rX rI rY )r= r, r- r: )r! r; r+ rR rN rS rX rT rU rH rI rY rZ r< r r r rP 6 s $z+CreateForeignKeyOp.batch_create_foreign_key)N)N)NNNNNNN)NNNNNN)r r r r r r0 r& r( r r$ r r> rO rP r r r r r � s* ! C r �create_check_constraint� batch_create_check_constraintc @ sh e Zd ZdZdZddd�Zedd� �Zddd �Zee � d d g�dd d ���Z ee � d g�dd� ��Z dS )r z.Represent a create check constraint operation.r4 Nc K s( || _ || _|| _|| _|| _|| _d S )N)r+ r, � conditionr- r. rB )r r+ r, r] r- r. rB r r r r0 p s z CreateCheckConstraintOp.__init__c C s$ t �|�}| |j|j|j|j|d�S )N)r- r. )r r5 r6 �sqltextr- )r! r" r8 r r r r z s z'CreateCheckConstraintOp.from_constraintc C s> | j d k r| j S t�|�}|j| j| j| jfd| ji| j��S )Nr- ) r. r rC r r+ r, r] r- rB )r rD rE r r r r$ � s z%CreateCheckConstraintOp.to_constraint)r6 r+ )rM r, c K s" | |||fd|i|��}|� |�S )a2 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 <value> 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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name * source -> table_name r- )r: )r! r; r+ r, r] r- rB r< r r r r[ � s :z/CreateCheckConstraintOp.create_check_constraintc K s* | ||j j|fd|j ji|��}|�|�S )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` .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> constraint_name r- )r= r, r- r: )r! r; r+ r] rB r< r r r r\ � s z5CreateCheckConstraintOp.batch_create_check_constraint)NN)N)N) r r r r r r0 r( r r$ r r> r[ r\ r r r r r h s 5r � create_index�batch_create_indexc @ sf e Zd ZdZddd�Zdd� Zdd � Zed d � �Zdd d �Z ee � dg�ddd���Z edd� �Z dS )� CreateIndexOpz#Represent a create index operation.NFc K s. || _ || _|| _|| _|| _|| _|| _d S )N)� index_namer, rA r- r3 rB � _orig_index)r rb r, rA r- r3 rc rB r r r r0 � s zCreateIndexOp.__init__c C s t �| �� �S )N)� DropIndexOp� from_index�to_index)r r r r r% � s zCreateIndexOp.reversec C s d| � � fS )NZ add_index)rf )r r r r r& � s zCreateIndexOp.to_diff_tuplec C s0 | |j |jj t�|�f|jj|j|d�|j��S )N)r- r3 rc )r6 �tabler Z_get_index_expressionsr- r3 �kwargs)r! �indexr r r re � s zCreateIndexOp.from_indexc C s> | j r | j S t�|�}|j| j| j| jf| j| jd�| j ��S )N)r- r3 ) rc r rC ri rb r, rA r- r3 rB )r rD rE r r r rf s zCreateIndexOp.to_index)r6 rb c K s$ | |||f||d�|��}|� |�S )aC 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)')]) .. versionadded:: 0.6.7 support for making use of the :func:`~sqlalchemy.sql.expression.text` construct in conjunction with :meth:`.Operations.create_index` in order to produce functional expressions within CREATE INDEX. :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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. :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 ``<dialectname>_<argname>``. See the documentation regarding an individual dialect at :ref:`dialect_toplevel` for detail on documented arguments. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> index_name )r- r3 )r: ) r! r; rb r, rA r- r3 rB r< r r r r_ s > zCreateIndexOp.create_indexc K s* | ||j j|fd|j ji|��}|�|�S )z�Issue a "create index" instruction using the current batch migration context. .. seealso:: :meth:`.Operations.create_index` r- )r= r, r- r: )r! r; rb rA rB r< r r r r` S s z CreateIndexOp.batch_create_index)NFN)N)NF)r r r r r0 r% r& r( re rf r r> r_ r` r r r r ra � s ?ra � drop_index�batch_drop_indexc @ st e Zd ZdZddd�Zdd� Zdd� Zed d � �Zdd d �Z ee � d dg�ddd���Z ee � d g�dd� ��Z dS )rd z!Represent a drop index operation.Nc C s || _ || _|| _|| _d S )N)rb r, r- rc )r rb r, r- rc r r r r0 j s zDropIndexOp.__init__c C s d| � � fS )NZ remove_index)rf )r r r r r& q s zDropIndexOp.to_diff_tuplec C s | j d krtd��t�| j �S )Nz:operation is not reversible; original index is not present)rc r1 ra re )r r r r r% t s zDropIndexOp.reversec C s | |j |jj |jj|d�S )N)r- rc )r6 rg r- )r! ri r r r re { s zDropIndexOp.from_indexc C s4 | j d k r| j S t�|�}|j| j| jdg| jd�S )N�x)r- )rc r rC ri rb r, r- )r rD rE r r r rf � s zDropIndexOp.to_index)r6 rb )Z tablenamer, c C s | |||d�}|� |�S )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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> index_name )r, r- )r: )r! r; rb r, r- r< r r r rj � s zDropIndexOp.drop_indexc K s | ||j j|j jd�}|�|�S )a) Issue a "drop index" instruction using the current batch migration context. .. seealso:: :meth:`.Operations.drop_index` .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> index_name )r, r- )r= r, r- r: )r! r; rb rB r< r r r rk � s z DropIndexOp.batch_drop_index)NNN)N)NN)r r r r r0 r& r% r( re rf r r> rj rk r r r r rd e s rd � create_tablec @ sX e Zd ZdZddd�Zdd� Zdd� Zed d � �Zdd d �Z ee � d g�dd� ��Z dS )� CreateTableOpz#Represent a create table operation.Nc K s" || _ || _|| _|| _|| _d S )N)r, rA r- rB � _orig_table)r r, rA r- ro rB r r r r0 � s zCreateTableOp.__init__c C s t �| �� �S )N)� DropTableOp� from_table�to_table)r r r r r% � s zCreateTableOp.reversec C s d| � � fS )NZ add_table)rr )r r r r r& � s zCreateTableOp.to_diff_tuplec C s. | |j t|j�t|j� f|j|d�|j��S )N)r- ro )r6 �listrK Z constraintsr- rh )r! rg r r r rq � s zCreateTableOp.from_tablec C s< | j d k r| j S t�|�}|j| jf| j�d| ji| j��S )Nr- )ro r rC rg r, rA r- rB )r rD rE r r r rr � s zCreateTableOp.to_table)r6 r, c O s | ||f|�}|� |�S )a� 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"}, ] ) .. versionadded:: 0.7.0 :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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. :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. .. versionadded:: 0.7.0 - the :class:`~sqlalchemy.schema.Table` object is returned. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> table_name )r: )r! r; r, rA rB r< r r r rm � s \zCreateTableOp.create_table)NN)N) r r r r r0 r% r& r( rq rr r r> rm r r r r rn � s rn � drop_tablec @ sZ e Zd ZdZddd�Zdd� Zdd� Zed d � �Zdd d �Z ee � d g�ddd���Z dS )rp z!Represent a drop table operation.Nc C s || _ || _|pi | _|| _d S )N)r, r- �table_kwro )r r, r- ru ro r r r r0 Q s zDropTableOp.__init__c C s d| � � fS )NZ remove_table)rr )r r r r r& X s zDropTableOp.to_diff_tuplec C s | j d krtd��t�| j �S )Nz:operation is not reversible; original table is not present)ro r1 rn rq )r r r r r% [ s zDropTableOp.reversec C s | |j |j|d�S )N)r- ro )r6 r- )r! rg r r r rq b s zDropTableOp.from_tablec C s6 | j d k r| j S t�|�}|j| jfd| ji| j��S )Nr- )ro r rC rg r, r- ru )r rD rE r r r rr f s zDropTableOp.to_table)r6 r, c K s | |||d�}|� |� 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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. :param \**kw: Other keyword arguments are passed to the underlying :class:`sqlalchemy.schema.Table` object created for the command. .. versionchanged:: 0.8.0 The following positional argument names have been changed: * name -> table_name )r- ru N)r: )r! r; r, r- rB r< r r r rt o s zDropTableOp.drop_table)NNN)N)N) r r r r r0 r& r% r( rq rr r r> rt r r r r rp M s rp c @ s e Zd ZdZddd�ZdS )� AlterTableOpz#Represent an alter table operation.Nc C s || _ || _d S )N)r, r- )r r, r- r r r r0 � s zAlterTableOp.__init__)N)r r r r r0 r r r r rv � s rv � rename_tablec s0 e Zd ZdZd� fdd� Zeddd��Z� ZS ) � RenameTableOpz#Represent a rename table operation.Nc s t t| �j||d� || _d S )N)r- )�superrx r0 �new_table_name)r �old_table_namerz r- )� __class__r r r0 � s zRenameTableOp.__init__c C s | |||d�}|� |�S )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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. )r- )r: )r! r; r{ rz r- r< r r r rw � s zRenameTableOp.rename_table)N)N)r r r r r0 r( rw � __classcell__r r )r| r rx � s rx � alter_column�batch_alter_columnc sb e Zd ZdZd� fdd� Zdd� Zdd � Zd d � Zee � d g�dd d���Z eddd��Z � Z S )� AlterColumnOpz$Represent an alter column operation.NFc sN t t| �j||d� || _|| _|| _|| _|| _|| _| | _ | | _ | | _ d S )N)r- ) ry r� r0 � column_name� existing_type�existing_server_default�existing_nullable�modify_nullable�modify_server_default� modify_name� modify_typerB ) r r, r� r- r� r� r� r� r� r� r� rB )r| r r r0 � s zAlterColumnOp.__init__c C s� g }| j | j| j }}}| jd k rJ|�d|||| j| jd�| j| jf� | jd k rz|�d|||| j| jd�| j| jf� | j dk r�|�d|||| j| jd�| j| j f� |S )Nr� )r� r� r� )r� r� FZmodify_default)r� r� ) r- r, r� r� �appendr� r� r� r� r� )r Zcol_diffr- �tnameZcnamer r r r& � s0 zAlterColumnOp.to_diff_tuplec C sL | j d k p | jdk p | jd k }|r&dS x | jD ]}|�d�r.dS q.W dS d S )NFTZmodify_)r� r� r� rB � startswith)r Zhc1rB r r r � has_changes� s zAlterColumnOp.has_changesc C s� | j �� }| j|d< | j|d< | j|d< | jd k r<| j|d< | jd k rP| j|d< | jdk rd| j|d< tdd � d d � |D �D ��}xD|D ]<}d | |kr�|d | }|d | |d | < ||d | < q�W | j | j | j fd| j i|��S )Nr� r� r� r� r� Fr� c s s | ]}|r|� d �V qdS )r N)�group)rJ �mr r r � <genexpr> s z(AlterColumnOp.reverse.<locals>.<genexpr>c S s g | ]}t �d |��qS )z^(?:existing_|modify_)(.+)$)�rerY )rJ �kr r r rL s z)AlterColumnOp.reverse.<locals>.<listcomp>z modify_%sz existing_%sr- ) rB �copyr� r� r� r� r� r� �setr| r, r� r- )r rB Zall_keysr� Zswapr r r r% s* zAlterColumnOp.reverse)r6 �new_column_namec K s. | ||f| || | ||||d�| ��} |� | �S )aX 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_server_default`` argument is used in this case as well to remove a previous constraint. :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 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 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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. )r- r� r� r� r� r� r� r� )r: )r! r; r, r� �nullable�server_defaultr� r/ r� r� r� r- rB �altr r r r~ ! s YzAlterColumnOp.alter_columnc K s6 | |j j|f|j j||| ||||d�| ��} |�| �S )z�Issue an "alter column" instruction using the current batch migration context. .. seealso:: :meth:`.Operations.add_column` )r- r� r� r� r� r� r� r� )r= r, r- r: ) r! r; r� r� r� r� r/ r� r� r� rB r� r r r r � s z AlterColumnOp.batch_alter_column)NNFNNFNN)NFNNNFNN)NFNNNFN)r r r r r0 r& r� r% r( r r> r~ r r} r r )r| r r� � s< ' \ r� � add_column�batch_add_columnc sl e Zd ZdZd� fdd� Zdd� Zdd� Zd d � Zed d � �Z ed d� �Z eddd��Z edd� �Z � Z S )� AddColumnOpz"Represent an add column operation.Nc s t t| �j||d� || _d S )N)r- )ry r� r0 �column)r r, r� r- )r| r r r0 � s zAddColumnOp.__init__c C s t �| j| j| j�S )N)� DropColumnOp�from_column_and_tablenamer- r, r� )r r r r r% � s zAddColumnOp.reversec C s d| j | j| jfS )Nr� )r- r, r� )r r r r r& � s zAddColumnOp.to_diff_tuplec C s | j S )N)r� )r r r r � to_column� s zAddColumnOp.to_columnc C s | |j j||j jd�S )N)r- )rg r6 r- )r! �colr r r � from_column� s zAddColumnOp.from_columnc C s | |||d�S )N)r- r )r! r- r� r� r r r r� � s z%AddColumnOp.from_column_and_tablenamec C s | |||d�}|� |�S )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 provided :class:`~sqlalchemy.schema.Column` object can also specify a :class:`~sqlalchemy.schema.ForeignKey`, referencing a remote table name. Alembic will automatically generate a stub "referenced" table and emit a second ALTER statement in order to add the constraint separately:: from alembic import op from sqlalchemy import Column, INTEGER, ForeignKey op.add_column('organization', Column('account_id', INTEGER, ForeignKey('accounts.id')) ) Note that this statement uses the :class:`~sqlalchemy.schema.Column` construct as is 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 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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. )r- )r: )r! r; r, r� r- r< r r r r� � s 7zAddColumnOp.add_columnc C s | |j j||j jd�}|�|�S )z�Issue an "add column" instruction using the current batch migration context. .. seealso:: :meth:`.Operations.add_column` )r- )r= r, r- r: )r! r; r� r< r r r r� s z AddColumnOp.batch_add_column)N)N)r r r r r0 r% r& r� r( r� r� r� r� r} r r )r| r r� � s 9r� � drop_column�batch_drop_columnc sb e Zd ZdZd� fdd� Zdd� Zdd� Zed d � �Zdd d �Z edd d��Z edd� �Z � Z S )r� z"Represent a drop column operation.Nc s* t t| �j||d� || _|| _|| _d S )N)r- )ry r� r0 r� rB � _orig_column)r r, r� r- r� rB )r| r r r0 s zDropColumnOp.__init__c C s d| j | j| �� fS )NZ remove_column)r- r, r� )r r r r r& s zDropColumnOp.to_diff_tuplec C s& | j d krtd��t�| j| j| j �S )Nz;operation is not reversible; original column is not present)r� r1 r� r� r- r, )r r r r r% # s zDropColumnOp.reversec C s | ||j ||d�S )N)r- r� )r6 )r! r- r� r� r r r r� , s z&DropColumnOp.from_column_and_tablenamec C s( | j d k r| j S t�|�}|�| jt�S )N)r� r rC r� r� r )r rD rE r r r r� 0 s zDropColumnOp.to_columnc K s | ||fd|i|��}|� |�S )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`. .. versionadded:: 0.7.0 'schema' can now accept a :class:`~sqlalchemy.sql.elements.quoted_name` construct. :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. .. versionadded:: 0.6.2 r- )r: )r! r; r, r� r- rB r< r r r r� 6 s .zDropColumnOp.drop_columnc C s | |j j||j jd�}|�|�S )z�Issue a "drop column" instruction using the current batch migration context. .. seealso:: :meth:`.Operations.drop_column` )r- )r= r, r- r: )r! r; r� r< r r r r� g s z DropColumnOp.batch_drop_column)NN)N)N) r r r r r0 r& r% r( r� r� r� r� r} r r )r| r r� s /r� � bulk_insertc @ s( e Zd ZdZddd�Zed dd��ZdS ) � BulkInsertOpz"Represent a bulk insert operation.Tc C s || _ || _|| _d S )N)rg �rows� multiinsert)r rg r� r� r r r r0 { s zBulkInsertOp.__init__c C s | |||d�}|� |� 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. .. versionadded:: 0.6.4 :meth:`.Operations.inline_literal` can now be used with :meth:`.Operations.bulk_insert`, and the :paramref:`~.Operations.bulk_insert.multiinsert` flag has been added to assist in this usage when running in "online" mode. :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. .. versionadded:: 0.6.4 )r� N)r: )r! r; rg r� r� r< r r r r� � s UzBulkInsertOp.bulk_insertN)T)T)r r r r r0 r( r� r r r r r� w s r� �executec @ s( e Zd ZdZddd�Zeddd��ZdS ) � ExecuteSQLOpz#Represent an execute SQL operation.Nc C s || _ || _d S )N)r^ �execution_options)r r^ r� r r r r0 � s zExecuteSQLOp.__init__c C s | ||d�}|� |�S )a� Execute the given SQL using the current migration context. 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. For full interaction with a connected database, use the "bind" available from the context:: from alembic import op connection = op.get_bind() Also note that any parameterized statement here *will not work* in offline mode - INSERT, UPDATE and DELETE statements which refer to literal values would need to render inline expressions. For simple use cases, the :meth:`.inline_literal` function can be used for **rudimentary** quoting of string values. For "bulk" inserts, consider using :meth:`.bulk_insert`. For example, to emit an UPDATE statement which is equally compatible with both online and offline mode:: 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')}) ) Note above we also used 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. :param sql: 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. * Pretty much anything that's "executable" as described in :ref:`sqlexpression_toplevel`. :param execution_options: Optional dictionary of execution options, will be passed to :meth:`sqlalchemy.engine.Connection.execution_options`. )r� )r: )r! r; r^ r� r< r r r r� � s @ zExecuteSQLOp.execute)N)N)r r r r r0 r( r� r r r r r� � s r� c @ s6 e Zd ZdZd dd�Zdd� Zdd� Zed d � �Zd S ) � OpContainerz-Represent a sequence of operations operation.r c C s || _ d S )N)�ops)r r� r r r r0 ' s zOpContainer.__init__c C s | j S )N)r� )r r r r �is_empty* s zOpContainer.is_emptyc C s t t�| ��S )N)rs r� � _ops_as_diffs)r r r r �as_diffs- s zOpContainer.as_diffsc c sD x>|j D ]4}t|d�r2x$| �|�D ] }|V q"W q|�� V qW d S )Nr� )r� �hasattrr� r& )r! Z migrationsr< Zsub_opr r r r� 0 s zOpContainer._ops_as_diffsN)r ) r r r r r0 r� r� r( r� r r r r r� % s r� c s* e Zd ZdZd� fdd� Zdd� Z� ZS )�ModifyTableOpszCContains a sequence of operations that all apply to a single Table.Nc s t t| ��|� || _|| _d S )N)ry r� r0 r, r- )r r, r� r- )r| r r r0 = s zModifyTableOps.__init__c C s& t | jttdd� | jD ���| jd�S )Nc S s g | ] }|� � �qS r )r% )rJ r< r r r rL F s z*ModifyTableOps.reverse.<locals>.<listcomp>)r� r- )r� r, rs �reversedr� r- )r r r r r% B s zModifyTableOps.reverse)N)r r r r r0 r% r} r r )r| r r� : s r� c s2 e Zd ZdZd � fdd� Zdd� Zdd � Z� ZS ) � UpgradeOpsz�contains a sequence of operations that would apply to the 'upgrade' stream of a script. .. seealso:: :ref:`customizing_revision` r �upgradesc s t t| �j|d� || _d S )N)r� )ry r� r0 � upgrade_token)r r� r� )r| r r r0 V s zUpgradeOps.__init__c C s& t tdd� | jD ���|jd d �< |S )Nc S s g | ] }|� � �qS r )r% )rJ r< r r r rL \ s z+UpgradeOps.reverse_into.<locals>.<listcomp>)rs r� r� )r � downgrade_opsr r r � reverse_intoZ s zUpgradeOps.reverse_intoc C s | � tg d��S )N)r� )r� � DowngradeOps)r r r r r% ` s zUpgradeOps.reverse)r r� )r r r r r0 r� r% r} r r )r| r r� L s r� c s* e Zd ZdZd� fdd� Zdd� Z� ZS ) r� z�contains a sequence of operations that would apply to the 'downgrade' stream of a script. .. seealso:: :ref:`customizing_revision` r � downgradesc s t t| �j|d� || _d S )N)r� )ry r� r0 �downgrade_token)r r� r� )r| r r r0 n s zDowngradeOps.__init__c C s t ttdd� | jD ���d�S )Nc S s g | ] }|� � �qS r )r% )rJ r< r r r rL u s z(DowngradeOps.reverse.<locals>.<listcomp>)r� )r� rs r� r� )r r r r r% r s zDowngradeOps.reverse)r r� )r r r r r0 r% r} r r )r| r r� d s r� c @ sv e Zd ZdZde� dddddfdd�Zedd� �Zejdd� �Zedd � �Z e jd d � �Z ed d � �Z ed d� �Z dS )�MigrationScripta� represents a migration script. E.g. when autogenerate encounters this object, this corresponds to the production of an actual script file. A normal :class:`.MigrationScript` object would contain a single :class:`.UpgradeOps` and a single :class:`.DowngradeOps` directive. These are accessible via the ``.upgrade_ops`` and ``.downgrade_ops`` attributes. In the case of an autogenerate operation that runs multiple times, such as the multiple database example in the "multidb" template, the ``.upgrade_ops`` and ``.downgrade_ops`` attributes are disabled, and instead these objects should be accessed via the ``.upgrade_ops_list`` and ``.downgrade_ops_list`` list-based attributes. These latter attributes are always available at the very least as single-element lists. .. versionchanged:: 0.8.1 the ``.upgrade_ops`` and ``.downgrade_ops`` attributes should be accessed via the ``.upgrade_ops_list`` and ``.downgrade_ops_list`` attributes if multiple autogenerate passes proceed on the same :class:`.MigrationScript` object. .. seealso:: :ref:`customizing_revision` Nc C s@ || _ || _|| _|| _|| _|| _| | _| | _|| _|| _ d S )N) �rev_id�message�imports�head�splice� branch_label� version_path� depends_on� upgrade_opsr� ) r r� r� r� r� r� r� r� r� r� r� r r r r0 � s zMigrationScript.__init__c C s0 t | j�dkrtd��n| js"dS | jd S dS )zzAn instance of :class:`.UpgradeOps`. .. seealso:: :attr:`.MigrationScript.upgrade_ops_list` r zrThis MigrationScript instance has a multiple-entry list for UpgradeOps; please use the upgrade_ops_list attribute.Nr )�len� _upgrade_opsr1 )r r r r r� � s zMigrationScript.upgrade_opsc C s. t �|�| _x | jD ]}t|t�st�qW d S )N)r �to_listr� � isinstancer� �AssertionError)r r� �elemr r r r� � s c C s0 t | j�dkrtd��n| js"dS | jd S dS )z~An instance of :class:`.DowngradeOps`. .. seealso:: :attr:`.MigrationScript.downgrade_ops_list` r zvThis MigrationScript instance has a multiple-entry list for DowngradeOps; please use the downgrade_ops_list attribute.Nr )r� �_downgrade_opsr1 )r r r r r� � s z MigrationScript.downgrade_opsc C s. t �|�| _x | jD ]}t|t�st�qW d S )N)r r� r� r� r� r� )r r� r� r r r r� � s c C s | j S )a A list of :class:`.UpgradeOps` instances. This is used in place of the :attr:`.MigrationScript.upgrade_ops` attribute when dealing with a revision operation that does multiple autogenerate passes. .. versionadded:: 0.8.1 )r� )r r r r �upgrade_ops_list� s z MigrationScript.upgrade_ops_listc C s | j S )a A list of :class:`.DowngradeOps` instances. This is used in place of the :attr:`.MigrationScript.downgrade_ops` attribute when dealing with a revision operation that does multiple autogenerate passes. .. versionadded:: 0.8.1 )r� )r r r r �downgrade_ops_list� s z"MigrationScript.downgrade_ops_list) r r r r r� r0 r' r� �setterr� r� r� r r r r r� z s r� )#� r r r Zsqlalchemy.typesr �baser r r� �objectr r Zregister_operationr# r r r r ra rd rn rp rv rx r� r� r� r� r� r� r� r� r� r� r r r r �<module> sz n p > z ~ a B w d caK