HEX

File: //usr/local/lib/python3.10/dist-packages/sqlalchemy/testing/__pycache__/provision.cpython-310.pyc
o

���gn9�@s�ddlmZddlZddlZddlmZddlmZddlmZddlmZdd	lm	Z	dd
l
mZddl
mZddl
mZe�e�ZdZGd
d�d�Zdd�Zdd�Zdd�Zdd�Zdd�Zejdd��Zdd�Zejdd��Zejdd ��Zd!d"�Zd#d$�Z d%d&�Z!ejd'd(��Z"ejd)d*��Z#d+d,�Z$e�%e$�d-d.��Z&ejd/d0��Z'ejd1d2��Z(ejd3d4��Z)ejd5d6��Z*d7d8�Z+ejd9d:��Z,ejd;d<��Z-ejd=d>��Z.ejd?d@��Z/ejdAdB��Z0ejddCdD�dEdF��Z1ejdGdH��Z2dS)I�)�annotationsN�)�config)�engines)�util�)�exc)�inspect)�url)�ddl��schemac@s>eZdZddd�Zedd��Zedd��Zdd	�Zd
d�ZdS)
�registerNcCsi|_||_dS�N)�fns�	decorator)�selfr�r�G/usr/local/lib/python3.10/dist-packages/sqlalchemy/testing/provision.py�__init__s
zregister.__init__cCst��d�|�S�N�*�r�for_db)�cls�fnrrr�init"sz
register.initcCst|��d�Srr)rrrrr�init_decorator&szregister.init_decoratorcs��fdd�}|S)Ncs(�jr��|�}�D]}|�j|<q
�Sr)rr)r�dbname��dbnamesrrr�decorate+s

z!register.for_db.<locals>.decorater)rr r!rrrr*szregister.for_dbcOszt|t�rt�|�}n
t|tj�r|}n|jj}|��}||jvr/|j||g|�Ri|��S|jd|g|�Ri|��Sr)	�
isinstance�str�sa_url�make_url�URL�dbr
�get_backend_namer)r�cfg�arg�kwr
�backendrrr�__call__4s

zregister.__call__r)	�__name__�
__module__�__qualname__r�classmethodrrrr-rrrrrs



rcC�0t�D]}t�d||jj�t||j|�qdS)NzCREATE database %s, URI %r)�_configs_for_db_operation�log�infor'r
�	create_db��follower_identr)rrr�create_follower_dbB�
�r9cCs�t�|���}|��|rt||�}i}t|||�d|d<t�||�}t|||�|�	��
�tj�
||||�}|r>|t_|rEt||�|S)N�global�scope)r$r%�get_dialect�load_provisioning�follower_url_from_main�update_db_optsr�testing_engine�post_configure_engine�connect�closer�Configr�ident�configure_follower)�db_url�options�file_configr8�dialect�db_opts�engr)rrr�setup_configHs 

rNcCr2)NzDROP database %s, URI %r)r3r4r5r'r
�drop_dbr7rrr�drop_follower_dber:rPccs��t�}t�t�}dd�dd�|D�D�}|D]\}}|��}||j�|�qi}|D]6\}}|j}	|��|	|vrIt|��||	�||	<}
n||	}
t||
�D]}||vrYqR|�|�|VqRq,dS)arGenerate a set of URLs to test given configured URLs plus additional
    driver names.

    Given:

    .. sourcecode:: text

        --dburi postgresql://db1          --dburi postgresql://db2          --dburi postgresql://db2          --dbdriver=psycopg2 --dbdriver=asyncpg?async_fallback=true

    Noting that the default postgresql driver is psycopg2,  the output
    would be:

    .. sourcecode:: text

        postgresql+psycopg2://db1
        postgresql+asyncpg://db1
        postgresql+psycopg2://db2
        postgresql+psycopg2://db3

    That is, for the driver in a --dburi, we want to keep that and use that
    driver for each URL it's part of .   For a driver that is only
    in --dbdrivers, we want to use it just once for one of the URLs.
    for a driver that is both coming from --dburi as well as --dbdrivers,
    we want to keep it in that dburi.

    Driver specific query options can be specified by added them to the
    driver name. For example, to enable the async fallback option for
    asyncpg::

    .. sourcecode:: text

        --dburi postgresql://db1          --dbdriver=asyncpg?async_fallback=true

    cSsg|]}||��f�qSr)r=)�.0�url_objrrr�
<listcomp>�s
��z$generate_db_urls.<locals>.<listcomp>cSsg|]}t�|��qSr)r$r%)rQrHrrrrS�sN)	�set�collections�defaultdict�get_driver_name�name�addr>�
difference�_generate_driver_urls)�db_urls�
extra_drivers�urls�!backend_to_driver_we_already_have�urls_plus_dialectsrRrK�driver_name�backend_to_driver_we_needr,�extra_per_backend�
driver_urlrrr�generate_db_urlsks6�'
��
�
��reccsz�|��}|�|�t||d�}|Vt|�D]#}d|vr&|�dd�\}}n|}d}t|||�}|r:|�|�|VqdS)N��?r)rW�discard�generate_driver_url�list�split�remove)r
r]�main_driver�drv�driver_only�	query_str�new_urlrrrr[�s �

��r[cCsP|��}|jd||fd�}|r|�|�}z|��W|Stjy'YdSw)Nz%s+%s)�
drivername)r(rT�update_query_stringr=r�NoSuchModuleError)r
�driverrpr,rqrrrri�s
�

��riccs��t�}tj��D]}|j��q	tj��D]}|jj}|��}||j|j	|j
f}||vr5|V|�|�qtj��D]}|j��q;dSr)rTrrE�all_configsr'�disposer
r(�username�host�databaserY)�hostsr)r
r,�	host_confrrrr3�s�
��r3cC�dSrr�r)rMrrr�"drop_all_schema_objects_pre_tables��rcCr}rrr~rrr�#drop_all_schema_objects_post_tables�r�r�cCs,t||�t||�tjjjrt||�t|�}d}tjj�	|�r)||j
|jf7}tj
|||d�t||�tjj�	|�r�|���I}|��D]
}|�t�t�|���qFtjj�	|�rz|j
|jfD] }|j|d�D]}|�t�tj||d���qiqaWd�dSWd�dS1s�wYdSdS)Nr)�consider_schemasr)r�
drop_viewsr�requirements�materialized_views�enabled�drop_materialized_viewsr	�schemas�enabled_for_config�test_schema�
test_schema_2r�drop_all_tablesr��	sequences�begin�get_sequence_names�executer�DropSequencer
�Sequence)r)rM�	inspectorr��conn�seq�schema_namerrr�drop_all_schema_objects�s<






������"��r�cCs
t|�}z|��}Wn	tyYn(w|���}|D]}|�t�t�|t�	����qWd�n1s6wYt
jj�
|�r�z	|j|jd�}Wn
tyUYdSw|���}|D]}|�t�tj|t�	�|jd���q]Wd�dS1s|wYdSdS)Nr)r	�get_view_names�NotImplementedErrorr�r�r�	_DropViewr
�Table�MetaDatarr�r�r�r�)r)rMr��
view_namesr��vnamerrrr�sB�
����
����"��r�cCs�t|�}|��}|���}|D]
}|�d|���qWd�n1s$wYtjj�|�r_|j|jd�}|���}|D]}|�d|j�d|���q>Wd�dS1sXwYdSdS)NzDROP MATERIALIZED VIEW r�.)	r	�get_materialized_view_namesr��exec_driver_sqlrr�r�r�r�)r)rMr��mview_namesr�r�rrrr�<s&
���
��"��r�cC�td|jf��)z�Dynamically create a database for testing.

    Used when a test run will employ multiple processes, e.g., when run
    via `tox` or `pytest -n4`.
    z"no DB creation routine for cfg: %s�r�r
�r)rMrFrrrr6Ps
�r6cCr�)z8Drop a database that we dynamically created for testing.zno DB drop routine for cfg: %sr�r�rrrrO\srOcs(t���}t|j�dkr�S�fdd�S)N�cs
�||�Srr)rHrL�_options�rrr�<lambda>gs
z'_adapt_update_db_opts.<locals>.<lambda>)r�inspect_getfullargspec�len�args)r�insprr�r�_adapt_update_db_optsbs
r�cC�dS)zCSet database options (db_opts) for a test database that we created.Nr)rHrLrIrrrr@j�r@cCr�)z�Perform extra steps after configuring an engine for testing.

    (For the internal dialects, currently only used by sqlite, oracle, mssql)
    Nr)r
�enginer8rrrrBor�rBcCst�|�}|j|d�S)z�Create a connection URL for a dynamically-created test database.

    :param url: the connection URL specified when the test run was invoked
    :param ident: the pytest-xdist "worker identifier" to be used as the
                  database name
    )rz)r$r%rT�r
rFrrrr?ws
r?cCr�)z@Create dialect-specific config settings for a follower database.Nr)r)rFrrrrG�srGcCr�)a[Remove databases that were created during the test process, after the
    process has ended.

    This is an optional step that is invoked for certain backends that do not
    reliably release locks on the database as long as a process is still in
    use. For the internal dialects, this is currently only necessary for
    mssql and oracle.
    Nrr�rrr�run_reap_dbs�r�r�cCs�t�d�t�t�}t�t�}i}t|��B}|D]7}|��}|�d�\}}t�	|�}||vr:|�
�||<||��|��|j
f}	||	�|�||	�|�qWd�n1sZwY|D]}	t||	�d}
||	}t|
|�qadS)NzReaping databases...� r)r4r5rUrVrT�open�striprkr$r%r=r>r(ryrYrjr�)�idents_filer^�idents�dialects�file_�line�db_namerHrR�url_keyr
rFrrr�reap_dbs�s,




���r�cCr�)aOSpecify keyword arguments for creating a temporary Table.

    Dialect-specific implementations of this method will return the
    kwargs that are passed to the Table method when creating a temporary
    table for testing, e.g., in the define_temp_tables method of the
    ComponentReflectionTest class in suite/test_reflection.py
    z.no temp table keyword args routine for cfg: %sr�r~rrr�temp_table_keyword_args�s	
�r�cCr}rr)r�
connectionrrr�prepare_for_drop_tables�r�r�cCr}rr)rr'�testclsrrr� stop_test_class_outside_fixtures�r�r�cCs|S)a�Specify table name for creating a temporary Table.

    Dialect-specific implementations of this method will return the
    name to use when creating a temporary table for testing,
    e.g., in the define_temp_tables method of the
    ComponentReflectionTest class in suite/test_reflection.py

    Default to just the base name since that's what most dialects will
    use. The mssql dialect's implementation will need a "#" prepended.
    r)r)rM�	base_namerrr�get_temp_table_name�sr�cCstd|jjf��)Nz9backend does not implement a schema name set function: %s�r�r'r
)r)�dbapi_connectionr�rrr� set_default_schema_on_connection�s
��r�F)�
set_lambda�sort_by_parameter_ordercCstd|jj����)a�return the backends insert..on conflict / on dupe etc. construct.

    while we should add a backend-neutral upsert construct as well, such as
    insert().upsert(), it's important that we continue to test the
    backend-specific insert() constructs since if we do implement
    insert().upsert(), that would be using a different codepath for the things
    we need to test like insertmanyvalues, etc.

    z3backend does not include an upsert implementation: r�)r)�table�	returningr�r�rrr�upsert�s
�r�cCs|S)z�Normalize sequence parameters for dialect that don't start with 1
    by default.

    The default implementation does nothing
    r)r)�sequencerrr�normalize_sequence�sr�)3�
__future__rrU�loggingrfrrrrr	r�r
r$�sqlrr
�	getLoggerr.r4�FOLLOWER_IDENTrr9rNrPrer[rrir3rr�r�r�r�r6rOr�rr@rBr?rGr�r�r�r�r�r�r�r�r�rrrr�<module>sx
%J


!!











�