o g@sdZddlmZddlZddlmZddlmZddlmZdd lm Z dd lm Z dd l m Z Gd d d Z Gddde ZdS)zGlobal database feature support policy. Provides decorators to mark tests requiring specific feature support from the target database. External dialect test suites should subclass SuiteRequirements to provide specific inclusion/exclusions. ) annotationsN)asyncio) exclusionsonly_on create_engine)util) QueuePoolc@s eZdZdS) RequirementsN)__name__ __module__ __qualname__rra/var/www/html/ecg_monitoring/venv/lib/python3.10/site-packages/sqlalchemy/testing/requirements.pyr sr c@s eZdZeddZeddZeddZeddZed d Zed d Z ed dZ eddZ eddZ eddZ eddZeddZeddZeddZeddZedd Zed!d"Zed#d$Zed%d&Zed'd(Zed)d*Zed+d,Zed-d.Zed/d0Zed1d2Zed3d4Zed5d6Zed7d8Zed9d:Z ed;d<Z!ed=d>Z"ed?d@Z#edAdBZ$edCdDZ%edEdFZ&edGdHZ'edIdJZ(edKdLZ)edMdNZ*edOdPZ+edQdRZ,edSdTZ-edUdVZ.edWdXZ/edYdZZ0ed[d\Z1ed]d^Z2ed_d`Z3edadbZ4edcddZ5ededfZ6edgdhZ7edidjZ8edkdlZ9edmdnZ:edodpZ;edqdrZedwdxZ?edydzZ@ed{d|ZAed}d~ZBeddZCeddZDeddZEeddZFeddZGeddZHeddZIeddZJeddZKeddZLeddZMeddZNeddZOeddZPeddZQeddZReddZSeddZTeddZUeddZVeddZWeddZXeddZYeddZZeddZ[eddZ\eddZ]eddZ^eddZ_eddZ`eddZaeddZbeddZcedd„ZdeddĄZeeddƄZfeddȄZgeddʄZhedd̄Ziedd΄ZjeddЄZkedd҄ZleddԄZmeddքZnedd؄ZoeddڄZpedd܄ZqeddބZreddZseddZteddZueddZveddZweddZxeddZyeddZzeddZ{eddZ|eddZ}eddZ~eddZeddZeddZeddZeddZeddZeddZeddZeddZed d Zed d Zd dZeddZeddZeddZeddZeddZeddZeddZeddZedd Zed!d"Zed#d$Zed%d&Zed'd(Zed)d*Zed+d,Zed-d.Zed/d0Zed1d2Zed3d4Zed5d6Zed7d8Zed9d:Zed;d<Zed=d>Zed?d@ZedAdBZedCdDZedEdFZedGdHZedIdJZedKdLZedMdNZedOdPZedQdRZedSdTZedUdVZedWdXZedYdZZed[d\Zd]d^Zed_d`ZedadbZedcddZededfZedgdhZedidjZedkdlZdmdnZedodpZedqdrZedsdtZedudvZedwdxZedydzZed{d|Zed}d~ZeddZeddZeddZeddZeddZeddZeddZɐddZʐddZeddZeddZ͐ddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZeddZedd„ZedÐdĄZedŐdƄZedǐdȄZedɐdʄZedːd̄Zed͐d΄ZedϐdЄZedѐd҄ZedӐdԄZedՐdքZdS(SuiteRequirementscCtS)z/target platform can emit basic CreateTable DDL.ropenselfrrr create_table%zSuiteRequirements.create_tablecCr)z-target platform can emit basic DropTable DDL.rrrrr drop_table+rzSuiteRequirements.drop_tablecCr)z>target platform supports IF NOT EXISTS / IF EXISTS for tables.rclosedrrrrtable_ddl_if_exists1rz%SuiteRequirements.table_ddl_if_existscCr)z?target platform supports IF NOT EXISTS / IF EXISTS for indexes.rrrrrindex_ddl_if_exists7rz%SuiteRequirements.index_ddl_if_existscCr)z0Return databases that support the UUID datatype.rrrrruuid_data_type=rz SuiteRequirements.uuid_data_typecCr)z*Target database must support foreign keys.rrrrr foreign_keysCrzSuiteRequirements.foreign_keyscCr)zKTarget database creates an index that's reflected for foreign keys.rrrrrforeign_keys_reflect_as_indexIz/SuiteRequirements.foreign_keys_reflect_as_indexcCr)z=Target database reflects unique indexes as unique constrains.rrrrr*unique_index_reflect_as_unique_constraintsPrzsz?SuiteRequirements.on_update_or_deferrable_fks..ronly_ifrrrron_update_or_deferrable_fkss z-SuiteRequirements.on_update_or_deferrable_fkscCdd}t|S)z"target database is using QueuePoolcSst|jjtSr+) isinstancedbpoolr configrrrgosz(SuiteRequirements.queue_pool..gor1rr:rrr queue_pools zSuiteRequirements.queue_poolcCr)z;Target database must support self-referential foreign keys.rrrrrself_referential_foreign_keysrz/SuiteRequirements.self_referential_foreign_keyscCr)z=Target database must support the DDL phrases for FOREIGN KEY.rrrrrforeign_key_ddlrz!SuiteRequirements.foreign_key_ddlcCr)z3target database must support names for constraints.rrrrrnamed_constraintsrz#SuiteRequirements.named_constraintscCr)z8target database must apply names to unnamed constraints.rrrrrimplicitly_named_constraintsrz.SuiteRequirements.implicitly_named_constraintscCr)atarget database allows column names that have unusual characters in them, such as dots, spaces, slashes, or percent signs. The column names are as always in such a case quoted, however the DB still needs to support those characters in the name somehow. rrrrrunusual_column_name_characterss z0SuiteRequirements.unusual_column_name_characterscCr)z(Target database must support subqueries.rrrrr subqueriesrzSuiteRequirements.subqueriescCr)zRtarget database can render OFFSET, or an equivalent, in a SELECT. rrrrroffsetzSuiteRequirements.offsetcCr)zWtarget database can render LIMIT and/or OFFSET using a bound parameter rrrrrbound_limit_offsetrDz$SuiteRequirements.bound_limit_offsetcCr)ztarget database can render LIMIT and/or OFFSET with a complete SQL expression, such as one that uses the addition operator. parameter rrrrrsql_expression_limit_offsetz-SuiteRequirements.sql_expression_limit_offsetcCr)zTarget database must support parenthesized SELECT in UNION when LIMIT/OFFSET is specifically present. E.g. (SELECT ...) UNION (SELECT ..) This is known to fail on SQLite. rrrrr/parens_in_union_contained_select_w_limit_offset zASuiteRequirements.parens_in_union_contained_select_w_limit_offsetcCr)alTarget database must support parenthesized SELECT in UNION when OFFSET/LIMIT is specifically not present. E.g. (SELECT ... LIMIT ..) UNION (SELECT .. OFFSET ..) This is known to fail on SQLite. It also fails on Oracle because without LIMIT/OFFSET, there is currently no step that creates an additional subquery. rrrrr0parens_in_union_contained_select_wo_limit_offsetr'zBSuiteRequirements.parens_in_union_contained_select_wo_limit_offsetcCr)z;Target database must support boolean expressions as columnsrrrrrboolean_col_expressionsrz)SuiteRequirements.boolean_col_expressionscCr)z5Target database allows boolean columns to store NULL.rrrrrnullable_booleansrz#SuiteRequirements.nullable_booleanscCr)z,Target backends that support nulls ordering.rrrrr nullsordering rzSuiteRequirements.nullsorderingcCr)ztarget database/driver supports bound parameters as column expressions without being in the context of a typed column. rrrrrstandalone_bindsr#z"SuiteRequirements.standalone_bindscCr)ztarget database/driver supports bound parameters with NULL in the WHERE clause, in situations where it has to be typed. rrrrr!standalone_null_binds_whereclauserDz3SuiteRequirements.standalone_null_binds_whereclausecCr)z5Target database must support INTERSECT or equivalent.rrrrr intersectzSuiteRequirements.intersectcCr)z?Target database must support EXCEPT or equivalent (i.e. MINUS).rrrrrexcept_$rQzSuiteRequirements.except_cCr)z.Target database must support window functions.rrrrrwindow_functions)rQz"SuiteRequirements.window_functionscCr)zTarget database supports CTEsrrrrrctes.rzSuiteRequirements.ctescCr)ztarget database supports CTES that ride on top of a normal UPDATE or DELETE statement which refers to the CTE in a correlated subquery. rrrrrctes_with_update_delete4rGz)SuiteRequirements.ctes_with_update_deletecCr)z}target database supports CTES which consist of INSERT, UPDATE or DELETE *within* the CTE, e.g. WITH x AS (UPDATE....)rrrrr ctes_on_dml=r#zSuiteRequirements.ctes_on_dmlcCr)z~target platform generates new surrogate integer primary key values when insert() is executed, excluding the pk column.rrrrrautoincrement_insertDr#z&SuiteRequirements.autoincrement_insertcCr)a#target platform will allow cursor.fetchone() to proceed after a COMMIT. Typically this refers to an INSERT statement with RETURNING which is invoked within "autocommit". If the row can be returned after the autocommit, then this rule can be open. rrrrrfetch_rows_post_commitKs z(SuiteRequirements.fetch_rows_post_commitcCr)ztarget platform supports SQL expressions in GROUP BY e.g. SELECT x + y AS somelabel FROM table GROUP BY x + y rrrrrgroup_by_complex_expressionXrIz-SuiteRequirements.group_by_complex_expressioncCtdddS)NcS |jjj Sr+)r6dialectsupports_sane_rowcountr8rrrr0g z1SuiteRequirements.sane_rowcount..z&driver doesn't support 'sane' rowcountrskip_ifrrrr sane_rowcountdzSuiteRequirements.sane_rowcountcCrZ)NcSr[r+)r6r\supports_sane_multi_rowcountr8rrrr0nr^z7SuiteRequirements.sane_multi_rowcount..z;driver %(driver)s %(doesnt_support)s 'sane' multi row countrfails_ifrrrrsane_multi_rowcountkrbz%SuiteRequirements.sane_multi_rowcountcCrZ)NcSr[r+)r6r\ supports_sane_rowcount_returningr8rrrr0usz=SuiteRequirements.sane_rowcount_w_returning..z;driver doesn't support 'sane' rowcount when returning is onrdrrrrsane_rowcount_w_returningrz+SuiteRequirements.sane_rowcount_w_returningcCrZ)zatarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent.cSs|jjjp|jjjp|jjjSr+)r6r\supports_empty_insertsupports_default_valuessupports_default_metavaluer8rrrr0  z1SuiteRequirements.empty_inserts..zempty inserts not supportedr1rrrr empty_inserts{szSuiteRequirements.empty_insertscC|jS)zvtarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent, within executemany())rnrrrrempty_inserts_executemanyz+SuiteRequirements.empty_inserts_executemanycCr)z.target platform supports INSERT from a SELECT.rrrrrinsert_from_selectrz$SuiteRequirements.insert_from_selectcCrZ)z.target platform supports DELETE ... RETURNING.cS |jjjSr+)r6r\delete_returningr8rrrr0 z4SuiteRequirements.delete_returning..z4%(database)s %(does_support)s 'DELETE ... RETURNING'r1rrrrrtz"SuiteRequirements.delete_returningcCrZ)z.target platform supports INSERT ... RETURNING.cSrsr+)r6r\insert_returningr8rrrr0ruz4SuiteRequirements.insert_returning..z4%(database)s %(does_support)s 'INSERT ... RETURNING'r1rrrrrwrvz"SuiteRequirements.insert_returningcCrZ)z.target platform supports UPDATE ... RETURNING.cSrsr+)r6r\update_returningr8rrrr0ruz4SuiteRequirements.update_returning..z4%(database)s %(does_support)s 'UPDATE ... RETURNING'r1rrrrrxrvz"SuiteRequirements.update_returningcCrZ)ztarget platform supports RETURNING when INSERT is used with executemany(), e.g. multiple parameter sets, indicating as many rows come back as do parameter sets were passed. cSrsr+)r6r\insert_executemany_returningr8rrrr0ruz@SuiteRequirements.insert_executemany_returning..zR%(database)s %(does_support)s 'RETURNING of multiple rows with INSERT executemany'r1rrrrryz.SuiteRequirements.insert_executemany_returningcCrZ)NcSs|jjjo|jjjo|jjjSr+)r6r\supports_multivalues_insertrwuse_insertmanyvaluesr8rrrr0rmz4SuiteRequirements.insertmanyvalues..z=%(database)s %(does_support)s 'insertmanyvalues functionalityr1rrrrinsertmanyvaluesriz"SuiteRequirements.insertmanyvaluescCr)zZTarget platform supports the syntax "(x, y) IN ((x1, y1), (x2, y2), ...)" rrrrrtuple_inrDzSuiteRequirements.tuple_incCro)z%Target platform tuple IN w/ empty set)r~rrrrtuple_in_w_emptysz"SuiteRequirements.tuple_in_w_emptycCr)zwtarget platform supports a SELECT statement that has the same name repeated more than once in the columns list.rrrrr%duplicate_names_in_cursor_descriptionr#z7SuiteRequirements.duplicate_names_in_cursor_descriptioncCrZ)z[Target database must have 'denormalized', i.e. UPPERCASE as case insensitive names.cSr[r+)r6r\requires_name_normalizer8rrrr0r^z6SuiteRequirements.denormalized_names..z,Backend does not require denormalized names.r_rrrrdenormalized_namesz$SuiteRequirements.denormalized_namescCrZ)zTtarget database must support multiple VALUES clauses in an INSERT statement.cSr[r+)r6r\r{r8rrrr0r^z7SuiteRequirements.multivalues_inserts..z*Backend does not support multirow inserts.r_rrrrmultivalues_insertsrz%SuiteRequirements.multivalues_insertscCr)zvtarget dialect implements the executioncontext.get_lastrowid() method without reliance on RETURNING. rrrrrimplements_get_lastrowidrDz*SuiteRequirements.implements_get_lastrowidcCr)zLdialect includes the required pep-249 attribute ``cursor.arraysize``rrrrr arraysizer#zSuiteRequirements.arraysizecCr)a<target dialect retrieves cursor.lastrowid, or fetches from a database-side function after an insert() construct executes, within the get_lastrowid() method. Only dialects that "pre-execute", or need RETURNING to get last inserted id, would return closed/fail/skip for this. rrrrremulated_lastrowidrIz$SuiteRequirements.emulated_lastrowidcCr)ztarget dialect retrieves cursor.lastrowid or an equivalent after an insert() construct executes, even if the table has a Sequence on it. rrrrr&emulated_lastrowid_even_with_sequences rGz8SuiteRequirements.emulated_lastrowid_even_with_sequencescCr)z]target platform includes a 'lastrowid' accessor on the DBAPI cursor object. rrrrrdbapi_lastrowidrDz!SuiteRequirements.dbapi_lastrowidcCr)z#Target database must support VIEWs.rrrrrviewsrzSuiteRequirements.viewscCs tddS)zXTarget database must support external schemas, and have one named 'test_schema'.cSrsr+)r6r\supports_schemasr8rrrr0%ruz+SuiteRequirements.schemas..rrrrrschemas  zSuiteRequirements.schemascCr)zJtarget system must support reflection of inter-schema foreign keysrrrrrcross_schema_fk_reflection'rz,SuiteRequirements.cross_schema_fk_reflectioncCr)aTarget supports reflection of FOREIGN KEY constraints and will return the name of the constraint that was used in the "CONSTRAINT FOREIGN KEY" DDL. MySQL prior to version 8 and MariaDB prior to version 10.5 don't support this. rrrrr&foreign_key_constraint_name_reflection-rIz8SuiteRequirements.foreign_key_constraint_name_reflectioncCr)ztarget system has a strong concept of 'default' schema that can be referred to implicitly. basically, PostgreSQL. rrrrrimplicit_default_schema9z)SuiteRequirements.implicit_default_schemacCr)z`target dialect implements provisioning module including set_default_schema_on_connectionrrrrrdefault_schema_name_switchCr#z,SuiteRequirements.default_schema_name_switchcCtddgdS)z0Target dialect must support server side cursors.cSrsr+)r6r\supports_server_side_cursorsr8rrrr0Oruz7SuiteRequirements.server_side_cursors..zno server side cursors supportr1rrrrserver_side_cursorsJz%SuiteRequirements.server_side_cursorscCr)z'Target database must support SEQUENCEs.cSrsr+)r6r\supports_sequencesr8rrrr0Xruz-SuiteRequirements.sequences..zno sequence supportr1rrrr sequencesSrzSuiteRequirements.sequencescCs t|jS)zJthe opposite of "sequences", DB does not support sequences at all.)r NotPredicaterrrrr no_sequences\rzSuiteRequirements.no_sequencescCr)zgTarget database supports sequences, but also optionally as a means of generating new PK values.cSs|jjjo |jjjSr+)r6r\rsequences_optionalr8rrrr0js z6SuiteRequirements.sequences_optional..z.no sequence support, or sequences not optionalr1rrrrrcs z$SuiteRequirements.sequences_optionalcCtddgS)atarget database / driver supports cursor.lastrowid as a means of retrieving the last inserted primary key value. note that if the target DB supports sequences also, this is still assumed to work. This is a new use case brought on by MariaDB 10.3. cSrsr+r6r\postfetch_lastrowidr8rrrr0zruz6SuiteRequirements.supports_lastrowid..r1rrrrsupports_lastrowidps z$SuiteRequirements.supports_lastrowidcCr)z"the opposite of supports_lastrowidcSr[r+rr8rrrr0r^z8SuiteRequirements.no_lastrowid_support..r1rrrrno_lastrowid_support}sz&SuiteRequirements.no_lastrowid_supportcCrr+rrrrrreflects_pk_namesr-z#SuiteRequirements.reflects_pk_namescCr)z8target database has general support for table reflectionrrrrrtable_reflectionrQz"SuiteRequirements.table_reflectioncCr)ztarget database supports creation and reflection of tables with no columns, or at least tables that seem to have no columns.rrrrrreflect_tables_no_columnsr#z+SuiteRequirements.reflect_tables_no_columnscCr)z:Indicates if the database support table comment reflectionrrrrrcomment_reflectionrQz$SuiteRequirements.comment_reflectioncCr)z{Indicates if the database support table comment reflection in the full unicode range, including emoji etc. rrrrrcomment_reflection_full_unicoder#z1SuiteRequirements.comment_reflection_full_unicodecCr)zVindicates if the database support comments on constraints and their reflectionrrrrrconstraint_comment_reflectionrz/SuiteRequirements.constraint_comment_reflectioncCro)ztarget database must support retrieval of the columns in a view, similarly to how a table is inspected. This does not include the full CREATE VIEW definition. rrrrrview_column_reflectionz(SuiteRequirements.view_column_reflectioncCro)zStarget database must support inspection of the full CREATE VIEW definition.rrrrrview_reflectionsz!SuiteRequirements.view_reflectioncCror+)rrrrrschema_reflectionz#SuiteRequirements.schema_reflectioncCr)zatarget database supports schema create and dropped with 'CREATE SCHEMA' and 'DROP SCHEMA'rrrrrschema_create_deleterz&SuiteRequirements.schema_create_deletecCrr+rrrrr!primary_key_constraint_reflectionr-z3SuiteRequirements.primary_key_constraint_reflectioncCrr+rrrrr!foreign_key_constraint_reflectionr-z3SuiteRequirements.foreign_key_constraint_reflectioncCrr+rrrrr1foreign_key_constraint_option_reflection_ondeleter-zCSuiteRequirements.foreign_key_constraint_option_reflection_ondeletecCrr+rrrrr1fk_constraint_option_reflection_ondelete_restrictr-zCSuiteRequirements.fk_constraint_option_reflection_ondelete_restrictcCrr+rrrrr1fk_constraint_option_reflection_ondelete_noactionr-zCSuiteRequirements.fk_constraint_option_reflection_ondelete_noactioncCrr+rrrrr1foreign_key_constraint_option_reflection_onupdater-zCSuiteRequirements.foreign_key_constraint_option_reflection_onupdatecCrr+rrrrr1fk_constraint_option_reflection_onupdate_restrictr-zCSuiteRequirements.fk_constraint_option_reflection_onupdate_restrictcCrr+rrrrrtemp_table_reflectionr-z'SuiteRequirements.temp_table_reflectioncCror+)rrrrrtemp_table_reflect_indexesrz,SuiteRequirements.temp_table_reflect_indexescCr)z8target dialect supports listing of temporary table namesrrrrrtemp_table_namesrQz"SuiteRequirements.temp_table_namescCr)z9target dialect supports checking a single temp table namerrrrrhas_temp_tablerQz SuiteRequirements.has_temp_tablecCr)z)target database supports temporary tablesrrrrrtemporary_tablesrQz"SuiteRequirements.temporary_tablescCr)z(target database supports temporary viewsrrrrrtemporary_viewsrQz!SuiteRequirements.temporary_viewscCrr+rrrrrindex_reflectionr-z"SuiteRequirements.index_reflectioncCrr+rrrrrindex_reflects_included_columnsr-z1SuiteRequirements.index_reflects_included_columnscCr)z?target database supports CREATE INDEX with per-column ASC/DESC.rrrrrindexes_with_ascdescrQz&SuiteRequirements.indexes_with_ascdesccCr)zKtarget database supports reflecting INDEX with per-column ASC/DESC.rrrrrreflect_indexes_with_ascdescrz.SuiteRequirements.reflect_indexes_with_ascdesccCr)zztarget database supports reflecting INDEX with per-column ASC/DESC but reflects them as expressions (like oracle).rrrrr*reflect_indexes_with_ascdesc_as_expression rztarget database supports CREATE INDEX against SQL expressions.rrrrrindexes_with_expressionsrQz*SuiteRequirements.indexes_with_expressionscCr)zLtarget database supports reflection of indexes with SQL expressions.rrrrr reflect_indexes_with_expressionsrz2SuiteRequirements.reflect_indexes_with_expressionscCr)z8target dialect supports reflection of unique constraintsrrrrrunique_constraint_reflectionrQz.SuiteRequirements.unique_constraint_reflectioncCr)z>target dialect supports reflection of inline check constraintsrrrrr"inline_check_constraint_reflection!rQz4SuiteRequirements.inline_check_constraint_reflectioncCr)z7target dialect supports reflection of check constraintsrrrrrcheck_constraint_reflection&rQz-SuiteRequirements.check_constraint_reflectioncCr)ztarget dialect raises IntegrityError when reporting an INSERT with a primary key violation. (hint: it should) rrrrr$duplicate_key_raises_integrity_error+rDz6SuiteRequirements.duplicate_key_raises_integrity_errorcCr)z3Target database must support VARCHAR with no lengthrrrrrunbounded_varchar3rz#SuiteRequirements.unbounded_varcharcCr)zTarget database/dialect can receive / deliver / compare data with non-ASCII characters in plain VARCHAR, TEXT columns, without the need for special "national" datatypes like NVARCHAR or similar. rrrrrunicode_data_no_special_types9rGz/SuiteRequirements.unicode_data_no_special_typescCr)zTarget database/dialect must support Python unicode objects with non-ASCII characters represented, delivered as bound parameters as well as in result rows. rrrrr unicode_dataBrGzSuiteRequirements.unicode_datacCr)zRTarget driver must support some degree of non-ascii symbol names. rrrrr unicode_ddlKr#zSuiteRequirements.unicode_ddlcCr)z?Target driver can create tables with a name like 'some " table'rrrrrsymbol_names_w_double_quoteRrQz-SuiteRequirements.symbol_names_w_double_quotecCr)ztarget dialect supports rendering of a datetime.timedelta as a literal string, e.g. via the TypeEngine.literal_processor() method. rrrrrdatetime_intervalWrDz#SuiteRequirements.datetime_intervalcCr)ztarget dialect supports rendering of a date, time, or datetime as a literal string, e.g. via the TypeEngine.literal_processor() method. rrrrrdatetime_literals_rGz#SuiteRequirements.datetime_literalscCr)zUtarget dialect supports representation of Python datetime.datetime() objects.rrrrrdatetimehr#zSuiteRequirements.datetimecCr)zvtarget dialect supports representation of Python datetime.datetime() with tzinfo with DateTime(timezone=True).rrrrrdatetime_timezoneor#z#SuiteRequirements.datetime_timezonecCr)zntarget dialect supports representation of Python datetime.time() with tzinfo with Time(timezone=True).rrrrr time_timezonevr#zSuiteRequirements.time_timezonecCr)ztarget dialect when given a date object will bind it such that the database server knows the object is a date, and not a plain string. rrrrrdate_implicit_bound}rGz%SuiteRequirements.date_implicit_boundcCr)ztarget dialect when given a time object will bind it such that the database server knows the object is a time, and not a plain string. rrrrrtime_implicit_boundrGz%SuiteRequirements.time_implicit_boundcCr)ztarget dialect when given a datetime object will bind it such that the database server knows the object is a datetime, and not a plain string. rrrrrdatetime_implicit_boundrGz)SuiteRequirements.datetime_implicit_boundcCr)zftarget dialect supports representation of Python datetime.datetime() with microsecond objects.rrrrrdatetime_microsecondsr#z'SuiteRequirements.datetime_microsecondscCr)ztarget dialect supports representation of Python datetime.datetime() with microsecond objects but only if TIMESTAMP is used.rrrrrtimestamp_microsecondsr#z(SuiteRequirements.timestamp_microsecondscCro)atarget dialect when given a datetime object which also includes a microseconds portion when using the TIMESTAMP data type will bind it such that the database server knows the object is a datetime with microseconds, and not a plain string. )rrrrr%timestamp_microseconds_implicit_boundrz7SuiteRequirements.timestamp_microseconds_implicit_boundcCrzutarget dialect supports representation of Python datetime.datetime() objects with historic (pre 1970) values.rrrrrdatetime_historicr#z#SuiteRequirements.datetime_historiccCr)zQtarget dialect supports representation of Python datetime.date() objects.rrrrrdater#zSuiteRequirements.datecCr)zPtarget dialect accepts a datetime object as the target of a date column.rrrrrdate_coerces_from_datetimer#z,SuiteRequirements.date_coerces_from_datetimecCrrrrrrr date_historicr#zSuiteRequirements.date_historiccCr)zQtarget dialect supports representation of Python datetime.time() objects.rrrrrtimer#zSuiteRequirements.timecCr)zbtarget dialect supports representation of Python datetime.time() with microsecond objects.rrrrrtime_microsecondsr#z#SuiteRequirements.time_microsecondscCr)zttarget database/driver can allow BLOB/BINARY fields to be compared against a bound parameter value. rrrrrbinary_comparisonsrDz$SuiteRequirements.binary_comparisonscCr)a=target backend supports simple binary literals, e.g. an expression like: .. sourcecode:: sql SELECT CAST('foo' AS BINARY) Where ``BINARY`` is the type emitted from :class:`.LargeBinary`, e.g. it could be ``BLOB`` or similar. Basically fails on Oracle. rrrrrbinary_literalsz!SuiteRequirements.binary_literalscCr)z:target dialect supports 'AUTOCOMMIT' as an isolation_levelrrrrr autocommitrQzSuiteRequirements.autocommitcCr)ztarget dialect supports general isolation level settings. Note that this requirement, when enabled, also requires that the get_isolation_levels() method be implemented. rrrrrisolation_levelrz!SuiteRequirements.isolation_levelc Csr|j*}z |j|jj}Wnty YWddSw|jj|dWdS1s2wYdS)aReturn a structure of supported isolation levels for the current testing dialect. The structure indicates to the testing suite what the expected "default" isolation should be, as well as the other values that are accepted. The dictionary has two keys, "default" and "supported". The "supported" key refers to a list of all supported levels and it should include AUTOCOMMIT if the dialect supports it. If the :meth:`.DefaultRequirements.isolation_level` requirement is not open, then this method has no return value. E.g.:: >>> testing.requirements.get_isolation_levels() { "default": "READ_COMMITTED", "supported": [ "SERIALIZABLE", "READ UNCOMMITTED", "READ COMMITTED", "REPEATABLE READ", "AUTOCOMMIT" ] } N)default supported)r6connectr\get_isolation_level_values connectiondbapi_connectionNotImplementedErrordefault_isolation_level)rr9connrrrrget_isolation_levelss  $z&SuiteRequirements.get_isolation_levelscCr4)ztarget dialect supports the :meth:`_engine.Dialect.get_isolation_level_values` method added in SQLAlchemy 2.0. c Ssh|j%}z |j|jjWnty YWddSw WddS1s-wYdSNFT)r6rr\rrrr)r9rrrrr:1s  $z8SuiteRequirements.get_isolation_level_values..gor1r;rrrr)s z,SuiteRequirements.get_isolation_level_valuescCr4)zctest that the dialect allows the 'isolation_level' argument to be handled by DefaultDialectcSs.z t|jjdd}WnYdS|jjdkS)NzREAD COMMITTED)rF)r r6urlr\_on_connect_isolation_level)r9errrr:Cs  zASuiteRequirements.dialect_level_isolation_level_param..gor1r;rrr#dialect_level_isolation_level_param>s z5SuiteRequirements.dialect_level_isolation_level_paramcCr)z.Target platform implements a native ARRAY typerrrrr array_typeQrQzSuiteRequirements.array_typecCr)z.target platform implements a native JSON type.rrrrr json_typeVrzSuiteRequirements.json_typecCro)zNtarget platform supports numeric array indexes within a JSON structure)rrrrrjson_array_indexes\rqz$SuiteRequirements.json_array_indexescCrr+rrrrr(json_index_supplementary_unicode_elementcr-z:SuiteRequirements.json_index_supplementary_unicode_elementcCr)zBackend has a JSON_EXTRACT or similar function that returns a valid JSON string in all cases. Used to test a legacy feature and is not needed. rrrrr!legacy_unconditional_json_extractgrz3SuiteRequirements.legacy_unconditional_json_extractcCr)zRtarget backend has general support for moderately high-precision numerics.rrrrrprecision_numerics_generalqrz,SuiteRequirements.precision_numerics_generalcCr)zbtarget backend supports Decimal() objects using E notation to represent very small values.rrrrr"precision_numerics_enotation_smallwrz4SuiteRequirements.precision_numerics_enotation_smallcCr)zbtarget backend supports Decimal() objects using E notation to represent very large values.rrrrr"precision_numerics_enotation_large}rz4SuiteRequirements.precision_numerics_enotation_largecCr)ztarget backend supports values with many digits on both sides, such as 319438950232418390.273596, 87673.594069654243 rrrrr*precision_numerics_many_significant_digitsrDzrz1SuiteRequirements.update_where_target_in_subquerycCr)zOtarget database must use a plain percent '%' as the 'modulus' operator.rrrrrmod_operator_as_percent_signPrz.SuiteRequirements.mod_operator_as_percent_signcCr)atarget backend supports weird identifiers with percent signs in them, e.g. 'some % column'. this is a very weird use case but often has problems because of DBAPIs that use python formatting. It's not a critical use case either. rrrrrpercent_schema_namesVrIz&SuiteRequirements.percent_schema_namescCr)ztarget database supports ordering by a column from a SELECT inside of a UNION E.g.: .. sourcecode:: sql (SELECT id, ...) UNION (SELECT id, ...) ORDER BY id rrrrrorder_by_col_from_unionbr'z)SuiteRequirements.order_by_col_from_unioncCr)a4target backend supports ORDER BY a column label within an expression. Basically this: .. sourcecode:: sql select data as foo from test order by foo || 'bar' Lots of databases including PostgreSQL don't support this, so this is off by default. rrrrrorder_by_label_with_expressionpsz0SuiteRequirements.order_by_label_with_expressioncsfdd}t|S)Ncs&z|WdStyYdSwr)get_order_by_collationrr8rrrchecks   z3SuiteRequirements.order_by_collation..checkr_rrrrrorder_by_collations  z$SuiteRequirements.order_by_collationcCstr+)rrr9rrrrsz(SuiteRequirements.get_order_by_collationcCr)zUTarget driver must support non-ASCII characters being passed at all. rrrrrunicode_connectionsr#z%SuiteRequirements.unicode_connectionscCr)zTarget driver must raise a DBAPI-level exception, such as InterfaceError, when the underlying connection has been closed and the execute() method is called. rrrrrgraceful_disconnectsrDz&SuiteRequirements.graceful_disconnectscCr)zU Target must support simultaneous, independent database connections. rrrrrindependent_connectionsr#z)SuiteRequirements.independent_connectionscCr)z Target must support simultaneous, independent database connections that will be used in a readonly fashion. rrrrr independent_readonly_connectionsrGz2SuiteRequirements.independent_readonly_connectionscCr)z9Catchall for a large variety of MySQL on Windows failuresrrrrrskip_mysql_on_windowsrQz'SuiteRequirements.skip_mysql_on_windowscCstddS)aTest environment must allow ad-hoc engine/connection creation. DBs that scale poorly for many connections, even when closed, i.e. Oracle, may use the "--low-connections" option which flags this requirement as not present. cS|jjSr+)optionslow_connectionsr8rrrr0z2SuiteRequirements.ad_hoc_engines..r_rrrrad_hoc_enginess z SuiteRequirements.ad_hoc_enginescCst|Sr+)rr`_running_on_windowsrrrr no_windowsszSuiteRequirements.no_windowscCstjddddS)NcSs tdkS)NWindows)platformsystemrrrrr0r^z7SuiteRequirements._running_on_windows..zrunning on Windows) description)rLambdaPredicaterrrrr%sz%SuiteRequirements._running_on_windowscCddlm}|jjSNrr8)r9 add_to_markertiming_intensiverrrrr0 z"SuiteRequirements.timing_intensivecCr,r-)r.r9r/memory_intensiverrrrr2r1z"SuiteRequirements.memory_intensivecCrZ)z}Mark tests that use threading and mock at the same time - stability issues have been observed with coverage cSr r+r! has_coverager8rrrr0r#z7SuiteRequirements.threading_with_mock..zStability issues with coverager_rrrrthreading_with_mocksz%SuiteRequirements.threading_with_mockcCr4)NcS$ztdWdStyYdSwNzsqlalchemy-stubs.ext.mypyFT __import__ ImportErrorr8rrrr   z2SuiteRequirements.sqlalchemy2_stubs..checkr1rrrrsqlalchemy2_stubs z#SuiteRequirements.sqlalchemy2_stubscCr4)NcSr6r7r8r8rrrrr;z5SuiteRequirements.no_sqlalchemy2_stubs..checkr_rrrrno_sqlalchemy2_stubsr=z&SuiteRequirements.no_sqlalchemy2_stubscCrZ)NcStjSr+)r py38rrrrr0z,SuiteRequirements.python38..zPython 3.8 or above requiredr1rrrrpython38zSuiteRequirements.python38cCrZ)NcSr?r+)r py39rrrrr0rAz,SuiteRequirements.python39..zPython 3.9 or above requiredr1rrrrpython39rCzSuiteRequirements.python39cCrZ)NcSr?r+)r py310rrrrr0rAz-SuiteRequirements.python310..zPython 3.10 or above requiredr1rrrr python310rCzSuiteRequirements.python310cCrZ)NcSr?r+)r py311rrrrr0rAz-SuiteRequirements.python311..zPython 3.11 or above requiredr1rrrr python311 rCzSuiteRequirements.python311cCrZ)NcSr?r+)r py312rrrrr0rAz-SuiteRequirements.python312..zPython 3.12 or above requiredr1rrrr python312rCzSuiteRequirements.python312cCrZ)NcSr?r+)r cpythonrrrrr0rAz+SuiteRequirements.cpython..zcPython interpreter neededr1rrrrrLrCzSuiteRequirements.cpythoncCrZ)NcSr?r+)r is64bitrrrrr0rAz+SuiteRequirements.is64bit..z64bit requiredr1rrrrrMszSuiteRequirements.is64bitcCsdd}t|dS)NcSr6)NpatchFTr8rrrr check_lib#r;z2SuiteRequirements.patch_library..check_libzpatch library neededr1)rrOrrr patch_library!s zSuiteRequirements.patch_librarycCro)ztarget platform must remove all cycles unconditionally when gc.collect() is called, as well as clean out unreferenced subclasses. )rLrrrrpredictable_gc-rz SuiteRequirements.predictable_gccCrZ)zTest should be skipped if coverage is enabled. This is to block tests that exercise libraries that seem to be sensitive to coverage, such as PostgreSQL notice logging. cSr r+r3r8rrrr0>r#z/SuiteRequirements.no_coverage..z(Issues observed when coverage is enabledr_rrrr no_coverage5rzzSuiteRequirements.no_coveragecCdSNFrrrrr_has_mysql_on_windowsBz'SuiteRequirements._has_mysql_on_windowscCrSrTrrrrr_has_mysql_fully_case_sensitiveErVz1SuiteRequirements._has_mysql_fully_case_sensitivecr.)Ncs Sr+) _has_sqliterrrrr0Jruz*SuiteRequirements.sqlite..r_rrrrsqliteHszSuiteRequirements.sqlitecCrZ)NcSs t Sr+)r has_compiled_extrrrrr0Oruz/SuiteRequirements.cextensions..zCython extensions not installedr_rrrr cextensionsLrbzSuiteRequirements.cextensionscCs0ddlm}z|dWdStyYdSw)Nrr z sqlite://TF) sqlalchemyr r:)rr rrrrXSs  zSuiteRequirements._has_sqlitecCr)z@dialect makes use of await_() to invoke operations on the DBAPI.rrrrr async_dialect\rzSuiteRequirements.async_dialectcCror+)greenletrrrrrbrzSuiteRequirements.asynciocCr4)NcSs$zddl}WdStyYdSw)NrTF)r^r:r9r^rrrr:hr;z)SuiteRequirements.no_greenlet..gor1r;rrr no_greenletfr=zSuiteRequirements.no_greenletcCr4)NcSs.tjsdSzddl}WdStyYdSw)NFrT) _test_asyncioENABLE_ASYNCIOr^r:r_rrrr:ts  z&SuiteRequirements.greenlet..gor1r;rrrr^rs zSuiteRequirements.greenletcCr)zSupports computed columnsrrrrrcomputed_columnsrQz"SuiteRequirements.computed_columnscCr)z/Supports computed columns with `persisted=True`rrrrrcomputed_columns_storedrQz)SuiteRequirements.computed_columns_storedcCr)z0Supports computed columns with `persisted=False`rrrrrcomputed_columns_virtualrQz*SuiteRequirements.computed_columns_virtualcCr)zSIf the default persistence is virtual or stored when `persisted` is omittedrrrrr"computed_columns_default_persistedrz4SuiteRequirements.computed_columns_default_persistedcCr)zTIf persistence information is returned by the reflection of computed columnsrrrrr"computed_columns_reflect_persistedrz4SuiteRequirements.computed_columns_reflect_persistedcCr)z1If a backend supports the DISTINCT ON in a selectrrrrrsupports_distinct_onrQz&SuiteRequirements.supports_distinct_oncCrZ)a Supports some form of "x IS [NOT] DISTINCT FROM y" construct. Different dialects will implement their own flavour, e.g., sqlite will emit "x IS NOT y" instead of "x IS DISTINCT FROM y". .. seealso:: :meth:`.ColumnOperators.is_distinct_from` cSr[r+)r6r\supports_is_distinct_fromr8rrrr0r^z=SuiteRequirements.supports_is_distinct_from..z4driver doesn't support an IS DISTINCT FROM constructr_rrrrris z+SuiteRequirements.supports_is_distinct_fromcCr)zKIf a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITYrrrrridentity_columnsrz"SuiteRequirements.identity_columnscCr)zIf a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY with a standard syntax. This is mainly to exclude MSSql. rrrrridentity_columns_standardrDz+SuiteRequirements.identity_columns_standardcCr)z+backend supports the regexp_match operator.rrrrr regexp_matchrQzSuiteRequirements.regexp_matchcCr)z-backend supports the regexp_replace operator.rrrrrregexp_replacerQz SuiteRequirements.regexp_replacecCr)z(backend supports the fetch first clause.rrrrr fetch_firstrQzSuiteRequirements.fetch_firstcCr)z5backend supports the fetch first clause with percent.rrrrr fetch_percentrQzSuiteRequirements.fetch_percentcCr)z2backend supports the fetch first clause with ties.rrrrr fetch_tiesrQzSuiteRequirements.fetch_tiescCr)z1backend supports the fetch first without order byrrrrrfetch_no_order_byrQz#SuiteRequirements.fetch_no_order_bycCr)zwbackend supports the offset when using fetch first with percent or ties. basically this is "not mssql" rrrrrfetch_offset_with_optionsr#z+SuiteRequirements.fetch_offset_with_optionscCr)zbackend supports fetch / offset with expression in them, like SELECT * FROM some_table OFFSET 1 + 1 ROWS FETCH FIRST 1 + 1 ROWS ONLY rrrrrfetch_expressionrGz"SuiteRequirements.fetch_expressioncCr)zIf autoincrement=True on a column does not require an explicit sequence. This should be false only for oracle. rrrrrautoincrement_without_sequencer#z0SuiteRequirements.autoincrement_without_sequencecCr)z=If X[Y] can be implemented with ``__class_getitem__``. py3.7+rrrrrgeneric_classesrQz!SuiteRequirements.generic_classescCr)z@indicates if the json_deserializer function is called with bytesrrrrrjson_deserializer_binaryrQz*SuiteRequirements.json_deserializer_binarycCr)z6Target database must support reflecting table_options.rrrrrreflect_table_optionsrQz'SuiteRequirements.reflect_table_optionscCr)z0Target database must support MATERIALIZED VIEWs.rrrrrmaterialized_viewsrQz$SuiteRequirements.materialized_viewscCr)z/Target database reflect MATERIALIZED VIEWs pks.rrrrrmaterialized_views_reflect_pkrQz/SuiteRequirements.materialized_views_reflect_pkcCr)z#Target database supports bitwise orrrrrrsupports_bitwise_or rQz%SuiteRequirements.supports_bitwise_orcCr)z$Target database supports bitwise andrrrrrsupports_bitwise_andrQz&SuiteRequirements.supports_bitwise_andcCr)z$Target database supports bitwise notrrrrrsupports_bitwise_notrQz&SuiteRequirements.supports_bitwise_notcCr)z$Target database supports bitwise xorrrrrrsupports_bitwise_xorrQz&SuiteRequirements.supports_bitwise_xorcCr)z4Target database supports bitwise left or right shiftrrrrrsupports_bitwise_shift!rQz(SuiteRequirements.supports_bitwise_shiftN)rrrpropertyrrrrr r!r"r$r%r&r(r)r*r,r3r<r=r>r?r@rArBrCrErFrHrJrKrLrMrNrOrPrRrSrTrUrVrWrXrYrarfrhrnrprrrtrwrxryr}r~rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr r r r r rrrrrrrrrrrrrrrr$r&r%r0r2r5r<r>rBrErGrIrKrLrMrPrQrRrUrWrYr[rXr]rr`r^rcrdrerfrgrhrirjrkrlrmrnrorprqrrrsrtrurvrwrxryrzr{r|r}r~rrrrr$s                                                                                                                                 &                r)__doc__ __future__rr(r.rrarrr r r7r r rrrrrs