mxiADLddlmZddlZddlZddlZddlmZddlmZddlmZddlm Z dd lm Z dd l m Z dd l m Z dd l mZdd lmZddlmZddlmZddlmZej*eZdZGddZdZdZdZdZdZej>dZ ej>dZ!dZ"ej>dZ#ej>dZ$dZ%dZ&dZ'ej>d Z(ej>d!Z)d"Z*ejWe*d#Z,ej>d$Z-ej>d%Z.ej>d&Z/ej>d'Z0ej>d(Z1d)Z2ej>d*Z3ej>d+Z4ej>d,Z5ej>d-Z6ej>d.Z7ej>dd/d0d1Z8ej>d2Z9ej>d3Z:ed4Z;ej>d5Z.decorate0s:~~^^B'! &#%  &Kr)rr)r*s`` rr zregister.for_db/s rc4|jd|g|i|Sr)r)rcfgargkws r call_originalzregister.call_original9s!txx}S-3-"--rct|trtj|}n`t|tjr|}nCt|t t fr|jj}n|jj}|j}||jvr|j||g|i|S|jd|g|i|Sr) isinstancestrsa_urlmake_urlURLr r enginer dbget_backend_namer)rr-r.r/r backends r__call__zregister.__call__<s c3 //#&C VZZ (C fj1 2**..C&&**C&&( dhh $488G$S535"5 5 488C=1s1b1 1rr) __name__ __module__ __qualname__r classmethodr#r%r r0r;r+rrrr"s>#**//. 2rrctD]D}tjd||jjt ||j|Fy)NzCREATE database %s, URI %r)_configs_for_db_operationloginfor8r create_dbfollower_identr-s rcreate_follower_dbrGLs=(*/ -~svvzzJ#svv~./rctj|j}|j|r t ||}i}t |||d|d<t j||}t||||jjtjj||||}|r |t_|r t|||S)Nglobalscope)r4r5 get_dialectload_provisioningfollower_url_from_mainupdate_db_optsrtesting_enginepost_configure_engineconnectcloserConfigridentconfigure_follower)db_urloptions file_configrFdialectdb_optsengr-s r setup_configr\Rsoof%113G '?G67G,GG   1C&#~6KKM -- gw DC% 3/ JrctD]D}tjd||jjt ||j|Fy)NzDROP database %s, URI %r)rArBrCr8r drop_dbrEs rdrop_follower_dbr_qs=(*- +^SVVZZHSVV^,-rc#TKt}tjt}|Dcgc]}tj|c}Dcgc]}||j f}}|D]3\}}|j }||jj|5i} |D]x\}}|j} |j| | vr#t|j|| x| | <} n| | } t|| D]} | |vr|j| | zycc}wcc}ww)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 N) set collections defaultdictr4r5rKget_driver_namenameaddrL difference_generate_driver_urls) db_urls extra_driversurls!backend_to_driver_we_already_haverVurl_objurls_plus_dialectsrY driver_namebackend_to_driver_we_needr:extra_per_backend driver_urls rgenerate_db_urlsrswsVN 5D(3(?(?(D%?FFF/F  '%%'( /I--/ )',,7;;KH I !#.,,!!# 3 3EHFj:7CD E %g .1B!:' B /9JK JT! HHZ    Gs(D(DD( D#$CD(c#K|j}|j|t||d}|t|D]E}d|vr|j dd\}}n|}d}t|||}|s1|j ||Gyw)N?r)rddiscardgenerate_driver_urllistsplitremove)r rj main_driverdrv driver_only query_strnew_urls rrhrhs%%'K+& c; 3C IM"  #:%(YYsA%6 "KKI%c; B    %M s A.B 1B c|jj|jj|jjjuS)zReturn True if the engine's URL is on the "default" driver, or more generally the "preferred" driver to use for tests. Backends can override this to make a different driver the "prefeferred" driver that's not the default.  drivername)r _get_entrypointrar9)r-r7s ris_preferred_driverrsK  ""$ ::>>zz224  /  rc|j}|j|d|}|r|j|} |j|S#tj $rYywxYw)N+r)r9raupdate_query_stringrKr NoSuchModuleError)r driverrr:rs rrxrxsr""$Ggg%v.G--i8  sAA$#A$c#"Kt}tjjD]}|jj tjjD]f}|jj }|j}||j|j|jf}||vsR||j|htjjD]}|jj ywr) rarrS all_configsr8disposer r9usernamehostdatabaserf)hostsr-r r: host_confs rrArAs EE}}((* }}((*!ffjj&&(cllCHHcllC E !I IIi !}}((* s B7D:ADcyrr+r-r[s r"drop_all_schema_objects_pre_tablesr rcyrr+rs r#drop_all_schema_objects_post_tablesrrrc t||t||tjjj r t ||t|}d}tjjj|r||j|jfz }tj|||t||tjjj|r|j!5}|j#D]9}|j%t'j(t+j,|;tjjj|rm|j|jfD]R}|j#|D];}|j%t'j(t+j,||=Tdddyy#1swYyxYw)Nr)consider_schemasr)r drop_viewsr requirementsmaterialized_viewsenableddrop_materialized_viewsr schemasenabled_for_config test_schema test_schema_2rdrop_all_tablesr sequencesbeginget_sequence_namesexecuter DropSequencerSequence)r-r[ inspectorrconnseq schema_names rdrop_all_schema_objectsrs&sC0sC --55S) I ""55c:S__c.?.?@@i:JK'S1 $$77< YY[ D 335 E S--fooc.BCD E""**==cB$'OOS5F5F#GK(;;* <  ,, &K H  =  s 7C#G$$G-c t|} |j}|j5}|D]L}|jt j t j|t jN dddtjjj|r |j|j}|j5}|D]X}|jt j t j|t j|jZ dddyy#1swYxYw#t$rYwxYw#1swYyxYw#t$rYywxYw)Nr)r get_view_namesrrr _DropViewrTableMetaDataNotImplementedErrorrrrrr)r-r[r view_namesrvnames rrr8sJ I --/ YY[ D#  MM&,,ufoo6G"HI   ""55c: "111IJ ' ELL "LL % & 1'*    ;         #   s<EAE2E.AE"E EE"E+. E:9E:ct|}|j}|j5}|D]}|jd| dddtj j j|r_|j|j}|j5}|D]#}|jd|jd|% dddyy#1swYxYw#1swYyxYw)NzDROP MATERIALIZED VIEW r.) r get_materialized_view_namesrexec_driver_sqlrrrrr)r-r[r mview_namesrrs rrrYs I779K D  DE  #:5'!B C DD""55c:;;??< YY[ D$ $$-coo->awG    ; DD  sC&)C&C#&C/c2td|j)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: rr r-r[rTs rrDrDms 039 rc2td|j)z8Drop a database that we dynamically created for testing.zno DB drop routine for cfg: rrs rr^r^ys #''K LLrcltj}t|jdk(rSfdS)Nc||Srr+)rVrZ_optionsr"s rz'_adapt_update_db_opts..sFG1Dr)rinspect_getfullargspeclenargs)r"insps` r_adapt_update_db_optsrs.  & &r *D 499~ DDrcy)zCSet database options (db_opts) for a test database that we created.Nr+)rVrZrWs rrNrNrcy)zPerform extra steps after configuring the main engine for testing. (For the internal dialects, currently only used by sqlite, oracle, mssql) Nr+)r r7rFs rrPrPrrcy)a perform extra steps after configuring any engine within the testing_engine() function. this includes the main engine as well as most ad-hoc testing engines. steps here should not get in the way of test cases that are looking for events, etc. Nr+)r r7rWrJs rpost_configure_testing_enginerrrcPtj|}|j|S)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 )r)r4r5rar rTs rrMrMs# //# C 77E7 ""rcy)z@Create dialect-specific config settings for a follower database.Nr+)r-rTs rrUrUs rcy)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. Nr+rs r run_reap_dbsrrrctjdtjt}tjt}i}t |5}|D]}|j }|jd\}}tj|}||vr&|j||<||j|j|jf} || j||| j| ddd|D]$} t|| d} || } t!| | &y#1swY3xYw)NzReaping databases... r)rBrCrbrcraopenstriprzr4r5rKrLr9rrfryr) idents_filerkidentsdialectsfile_linedb_namerVrmurl_keyr rTs rreap_dbsrs*HH #$  " "3 'D  $ $S )FH k  )e )D::|j|j^ycc}}w#1swYoxYw)zan absolutely foolproof delete from all tables routine. dialects should override this to add special instructions like disable constraints etc. savepointsFNr)getattrrrr reversedrtablesvaluesreget_table_namesr begin_nestedrdelete)rr-metadatarrtfksrs rdelete_from_all_tablesr 7s))<?J''  #I8&&( C})331883DD   / ((* 3""5<<>2 3 3   u||~ .!/  3 3s6C: / DD )= __future__rrbrloggingrurrrr r r7r r r r4rrsqlrr getLoggerr<rBFOLLOWER_IDENTrrGr\r_rsrhr#rrxrArrrrrrDr^rr%rNrPrrMrUrrrrrrrrrrrr r+rrrs#"0g!'2'2T/ >- GT,     "&      BB(  MM E ./N0N     ##    !2              )-u"  $$     //r