o gn9@sddlmZddlZddlZddlmZddlmZddlmZddlmZdd lm Z dd l m Z dd l mZdd l mZeeZdZGd ddZddZddZddZddZddZejddZddZejddZejdd Zd!d"Zd#d$Z d%d&Z!ejd'd(Z"ejd)d*Z#d+d,Z$e%e$d-d.Z&ejd/d0Z'ejd1d2Z(ejd3d4Z)ejd5d6Z*d7d8Z+ejd9d:Z,ejd;d<Z-ejd=d>Z.ejd?d@Z/ejdAdBZ0ejddCdDdEdFZ1ejdGdHZ2dS)I) annotationsN)config)engines)util)exc)inspect)url)ddlschemac@s>eZdZd ddZeddZeddZdd Zd d ZdS) registerNcCsi|_||_dSN)fns decorator)selfrr^/var/www/html/ecg_monitoring/venv/lib/python3.10/site-packages/sqlalchemy/testing/provision.py__init__s zregister.__init__cCstd|SN*rfor_db)clsfnrrrinit"sz register.initcCst|dSrr)rrrrrinit_decorator&szregister.init_decoratorcsfdd}|S)Ncs(jr|}D]}|j|<q Sr)rr)rdbnamedbnamesrrrdecorate+s   z!register.for_db..decorater)rr r!rrrr*szregister.for_dbcOszt|tr t|}n t|tjr|}n|jj}|}||jvr/|j||g|Ri|S|jd|g|Ri|Sr) isinstancestrsa_urlmake_urlURLdbr get_backend_namer)rcfgargkwr backendrrr__call__4s    zregister.__call__r) __name__ __module__ __qualname__r classmethodrrrr-rrrrrs    rcC0tD]}td||jjt||j|qdS)NzCREATE database %s, URI %r)_configs_for_db_operationloginfor'r create_dbfollower_identr)rrrcreate_follower_dbB r9cCst|}||rt||}i}t|||d|d<t||}t|||| t j ||||}|r>|t _|rEt|||S)Nglobalscope)r$r% get_dialectload_provisioningfollower_url_from_mainupdate_db_optsrtesting_enginepost_configure_engineconnectcloserConfigridentconfigure_follower)db_urloptions file_configr8dialectdb_optsengr)rrr setup_configHs       rNcCr2)NzDROP database %s, URI %r)r3r4r5r'r drop_dbr7rrrdrop_follower_dber:rPc cst}tt}dddd|DD}|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|]}||fqSr)r=).0url_objrrr s z$generate_db_urls..cSsg|]}t|qSr)r$r%)rQrHrrrrSsN) set collections defaultdictget_driver_namenameaddr> difference_generate_driver_urls) db_urls extra_driversurls!backend_to_driver_we_already_haveurls_plus_dialectsrRrK driver_namebackend_to_driver_we_needr,extra_per_backend driver_urlrrrgenerate_db_urlsks6'       reccsz|}||t||d}|Vt|D]#}d|vr&|dd\}}n|}d}t|||}|r:|||VqdS)N?r)rWdiscardgenerate_driver_urllistsplitremove)r r] main_driverdrv driver_only query_strnew_urlrrrr[s      r[cCsP|}|jd||fd}|r||}z|W|Stjy'YdSw)Nz%s+%s) drivername)r(rTupdate_query_stringr=rNoSuchModuleError)r driverrpr,rqrrrris   riccst}tjD]}|jq tjD]}|jj}|}||j|j |j f}||vr5|V| |qtjD]}|jq;dSr) rTrrE all_configsr'disposer r(usernamehostdatabaserY)hostsr)r r, host_confrrrr3s   r3cCdSrrr)rMrrr"drop_all_schema_objects_pre_tablesrcCr}rrr~rrr#drop_all_schema_objects_post_tablesrrc Cs,t||t||tjjjrt||t|}d}tjj |r)||j |j f7}t j |||dt||tjj |r|I}|D] }|tt|qFtjj |rz|j |j fD] }|j|dD]}|ttj||dqiqaWddSWddS1swYdSdS)Nr)consider_schemasr )r drop_viewsr requirementsmaterialized_viewsenableddrop_materialized_viewsr schemasenabled_for_config test_schema test_schema_2rdrop_all_tablesr sequencesbeginget_sequence_namesexecuter DropSequencer Sequence)r)rM inspectorrconnseq schema_namerrrdrop_all_schema_objectss<         "rc Cs t|}z|}Wn tyYn(w|}|D]}|tt|t qWdn1s6wYt j j |rz |j|jd}Wn tyUYdSw|}|D]}|ttj|t |jdq]WddS1s|wYdSdS)Nr )r get_view_namesNotImplementedErrorrrr _DropViewr TableMetaDatarrrrr)r)rMr view_namesrvnamerrrrsB     "rcCst|}|}|}|D] }|d|qWdn1s$wYtjj|r_|j|jd}|}|D]}|d|jd|q>WddS1sXwYdSdS)NzDROP MATERIALIZED VIEW r .) r get_materialized_view_namesrexec_driver_sqlrrrrr)r)rMr mview_namesrrrrrr<s&  "rcCtd|jf)zDynamically 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: %srr r)rMrFrrrr6Ps r6cCr)z8Drop a database that we dynamically created for testing.zno DB drop routine for cfg: %srrrrrrO\srOcs(t}t|jdkrSfddS)Ncs ||Srr)rHrL_optionsrrrgs z'_adapt_update_db_opts..)rinspect_getfullargspeclenargs)rinsprrr_adapt_update_db_optsbs  rcCdS)zCSet database options (db_opts) for a test database that we created.Nr)rHrLrIrrrr@jr@cCr)zPerform extra steps after configuring an engine for testing. (For the internal dialects, currently only used by sqlite, oracle, mssql) Nr)r enginer8rrrrBorrBcCst|}|j|dS)zCreate 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%rTr rFrrrr?ws  r?cCr)z@Create dialect-specific config settings for a follower database.Nr)r)rFrrrrGsrGcCr)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. Nrrrrr run_reap_dbsrrc Cstdtt}tt}i}t|B}|D]7}|}|d\}}t |}||vr:| ||<|| | |j f} || ||| |qWdn1sZwY|D]} t|| d} || } t| | qadS)NzReaping databases... r)r4r5rUrVrTopenstriprkr$r%r=r>r(ryrYrjr) idents_filer^identsdialectsfile_linedb_namerHrRurl_keyr rFrrrreap_dbss,         rcCr)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: %srr~rrrtemp_table_keyword_argss rcCr}rr)r connectionrrrprepare_for_drop_tablesrrcCr}rr)rr'testclsrrr stop_test_class_outside_fixturesrrcCs|S)aSpecify 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_namerrrget_temp_table_names rcCstd|jjf)Nz9backend does not implement a schema name set function: %srr'r )r)dbapi_connectionrrrr set_default_schema_on_connections rF) set_lambdasort_by_parameter_ordercCstd|jj)areturn 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 returningrrrrrupserts rcCs|S)zNormalize sequence parameters for dialect that don't start with 1 by default. The default implementation does nothing r)r)sequencerrrnormalize_sequencesr)3 __future__rrUloggingrfrrrrr rr r$sqlr r getLoggerr.r4FOLLOWER_IDENTrr9rNrPrer[rrir3rrrrrr6rOrrr@rBr?rGrrrrrrrrrrrrrsx          %J   !!