U a@shdZddlZddlZddlmZddlmZddlmZddlmZGd d d e Z Gd d d e Z dS) 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. N) exclusionsonly_on)util) QueuePoolc@s eZdZdS) RequirementsN)__name__ __module__ __qualname__r r `C:\Users\vtejo\AppData\Local\Temp\pip-unpacked-wheel-nyjtotrf\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؄ZoddڄZpedd܄ZqeddބZreddZseddZteddZueddZveddZweddZxeddZyeddZzeddZ{eddZ|eddZ}eddZ~eddZeddZeddZeddZeddZeddZeddZeddZeddZed d Zed d Zed dZeddZeddZeddZeddZeddZddZeddZeddZedd Zed!d"Zed#d$Zed%d&Zd'd(Zed)d*Zed+d,Zed-d.Zed/d0Zed1d2Zed3d4Zed5d6Zed7d8Zed9d:Zed;d<Zed=d>Zed?d@ZedAdBZedCdDZedEdFZdGdHZdIdJZedKdLZedMdNZdOdPZedQdRZedSdTZedUdVZedWdXZedYdZZed[d\Zed]d^Zed_d`ZedadbZedcddZededfZedgdhZedidjZedkdlZedmdnZedodpZedqdrZedsdtZduS(vSuiteRequirementscCstS)z/target platform can emit basic CreateTable DDL.ropenselfr r r create_table szSuiteRequirements.create_tablecCstS)z-target platform can emit basic DropTable DDL.rrr r r drop_table&szSuiteRequirements.drop_tablecCstS)z>target platform supports IF NOT EXISTS / IF EXISTS for tables.rclosedrr r rtable_ddl_if_exists,sz%SuiteRequirements.table_ddl_if_existscCstS)z?target platform supports IF NOT EXISTS / IF EXISTS for indexes.rrr r rindex_ddl_if_exists2sz%SuiteRequirements.index_ddl_if_existscCstS)z*Target database must support foreign keys.rrr r r foreign_keys8szSuiteRequirements.foreign_keyscCstS)zDatabase / dialect supports a query like:: SELECT * FROM VALUES ( (c1, c2), (c1, c2), ...) AS some_table(col1, col2) SQLAlchemy generates this with the :func:`_sql.values` function. rrr r rtable_value_constructor>s z)SuiteRequirements.table_value_constructorcCstS)aTarget database passes SQL-92 style statements to cursor.execute() when a statement like select() or insert() is run. A very small portion of dialect-level tests will ensure that certain conditions are present in SQL strings, and these tests use very basic SQL that will work on any SQL-like platform in order to assert results. It's normally a given for any pep-249 DBAPI that a statement like "SELECT id, name FROM table WHERE some_table.id=5" will work. However, there are dialects that don't actually produce SQL Strings and instead may work with symbolic objects instead, or dialects that aren't working with SQL, so for those this requirement can be marked as excluded. rrr r rstandard_cursor_sqlJsz%SuiteRequirements.standard_cursor_sqlcCstS)zQtarget database must support ON UPDATE..CASCADE behavior in foreign keys.rrr r ron_update_cascade^sz#SuiteRequirements.on_update_cascadecCstS)zWtarget database must *not* support ON UPDATE..CASCADE behavior in foreign keys.rrr r rnon_updating_cascadeesz&SuiteRequirements.non_updating_cascadecCstSNrrr r rdeferrable_fksksz SuiteRequirements.deferrable_fkscstfddS)NcsjjpjjSr)rZenabledr r rr rusz?SuiteRequirements.on_update_or_deferrable_fks..ronly_ifrr rron_update_or_deferrable_fksos z-SuiteRequirements.on_update_or_deferrable_fkscCsdd}t|S)z"target database is using QueuePoolcSst|jjtSr) isinstancedbpoolrconfigr r rgo}sz(SuiteRequirements.queue_pool..gor")rr*r r r queue_poolyszSuiteRequirements.queue_poolcCstS)z;Target database must support self-referential foreign keys.rrr r rself_referential_foreign_keyssz/SuiteRequirements.self_referential_foreign_keyscCstS)z=Target database must support the DDL phrases for FOREIGN KEY.rrr r rforeign_key_ddlsz!SuiteRequirements.foreign_key_ddlcCstS)z3target database must support names for constraints.rrr r rnamed_constraintssz#SuiteRequirements.named_constraintscCstS)z(Target database must support subqueries.rrr r r subqueriesszSuiteRequirements.subqueriescCstS)zRtarget database can render OFFSET, or an equivalent, in a SELECT. rrr r roffsetszSuiteRequirements.offsetcCstS)zWtarget database can render LIMIT and/or OFFSET using a bound parameter rrr r rbound_limit_offsetsz$SuiteRequirements.bound_limit_offsetcCstS)ztarget database can render LIMIT and/or OFFSET with a complete SQL expression, such as one that uses the addition operator. parameter rrr r rsql_expression_limit_offsetsz-SuiteRequirements.sql_expression_limit_offsetcCstS)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. rrr r r/parens_in_union_contained_select_w_limit_offsets zASuiteRequirements.parens_in_union_contained_select_w_limit_offsetcCstS)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. rrr r r0parens_in_union_contained_select_wo_limit_offsets zBSuiteRequirements.parens_in_union_contained_select_wo_limit_offsetcCstS)z;Target database must support boolean expressions as columnsrrr r rboolean_col_expressionssz)SuiteRequirements.boolean_col_expressionscCstS)z5Target database allows boolean columns to store NULL.rrr r rnullable_booleanssz#SuiteRequirements.nullable_booleanscCstS)z,Target backends that support nulls ordering.rrr r r nullsorderingszSuiteRequirements.nullsorderingcCstS)ztarget database/driver supports bound parameters as column expressions without being in the context of a typed column. rrr r rstandalone_bindssz"SuiteRequirements.standalone_bindscCstS)ztarget database/driver supports bound parameters with NULL in the WHERE clause, in situations where it has to be typed. rrr r r!standalone_null_binds_whereclausesz3SuiteRequirements.standalone_null_binds_whereclausecCstS)z5Target database must support INTERSECT or equivalent.rrr r r intersectszSuiteRequirements.intersectcCstS)z?Target database must support EXCEPT or equivalent (i.e. MINUS).rrr r rexcept_szSuiteRequirements.except_cCstS)z.Target database must support window functions.rrr r rwindow_functionssz"SuiteRequirements.window_functionscCstS)zTarget database supports CTEsrrr r rctesszSuiteRequirements.ctescCstS)ztarget database supports CTES that ride on top of a normal UPDATE or DELETE statement which refers to the CTE in a correlated subquery. rrr r rctes_with_update_deletesz)SuiteRequirements.ctes_with_update_deletecCstS)z}target database supports CTES which consist of INSERT, UPDATE or DELETE *within* the CTE, e.g. WITH x AS (UPDATE....)rrr r r ctes_on_dml szSuiteRequirements.ctes_on_dmlcCstS)z~target platform generates new surrogate integer primary key values when insert() is executed, excluding the pk column.rrr r rautoincrement_insertsz&SuiteRequirements.autoincrement_insertcCstS)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. rrr r rfetch_rows_post_commits z(SuiteRequirements.fetch_rows_post_commitcCstS)ztarget platform supports SQL expressions in GROUP BY e.g. SELECT x + y AS somelabel FROM table GROUP BY x + y rrr r rgroup_by_complex_expression(s z-SuiteRequirements.group_by_complex_expressioncCstdddS)NcSs |jjj Sr)r&dialectZsupports_sane_rowcountr(r r rr!7z1SuiteRequirements.sane_rowcount..z&driver doesn't support 'sane' rowcountrskip_ifrr r r sane_rowcount4szSuiteRequirements.sane_rowcountcCstdddS)NcSs |jjj Sr)r&rCZsupports_sane_multi_rowcountr(r r rr!>rDz7SuiteRequirements.sane_multi_rowcount..z;driver %(driver)s %(doesnt_support)s 'sane' multi row countrZfails_ifrr r rsane_multi_rowcount;sz%SuiteRequirements.sane_multi_rowcountcCstdddS)NcSs |jjj Sr)r&rCZ supports_sane_rowcount_returningr(r r rr!Esz=SuiteRequirements.sane_rowcount_w_returning..z;driver doesn't support 'sane' rowcount when returning is onrHrr r rsane_rowcount_w_returningBsz+SuiteRequirements.sane_rowcount_w_returningcCstdddS)zatarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent.cSs|jjjp|jjjp|jjjSr)r&rCZsupports_empty_insertZsupports_default_valuesZsupports_default_metavaluer(r r rr!Qs z1SuiteRequirements.empty_inserts..zempty inserts not supportedr"rr r r empty_insertsKszSuiteRequirements.empty_insertscCs|jS)zvtarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent, within executemany())rKrr r rempty_inserts_executemanyWsz+SuiteRequirements.empty_inserts_executemanycCstS)z.target platform supports INSERT from a SELECT.rrr r rinsert_from_select^sz$SuiteRequirements.insert_from_selectcCstdddS)zbtarget platform supports RETURNING completely, including multiple rows returned. cSs |jjjSr)r&rCfull_returningr(r r rr!lrDz2SuiteRequirements.full_returning..z:%(database)s %(does_support)s 'RETURNING of multiple rows'r"rr r rrNdsz SuiteRequirements.full_returningcCstdddS)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. cSs |jjjSr)r&rCinsert_executemany_returningr(r r rr!yrDz@SuiteRequirements.insert_executemany_returning..zR%(database)s %(does_support)s 'RETURNING of multiple rows with INSERT executemany'r"rr r rrOpsz.SuiteRequirements.insert_executemany_returningcCstdddS)ztarget platform supports RETURNING for at least one row. .. seealso:: :attr:`.Requirements.full_returning` cSs |jjjSr)r&rCZimplicit_returningr(r r rr!rDz-SuiteRequirements.returning..z9%(database)s %(does_support)s 'RETURNING of a single row'r"rr r r returning~s zSuiteRequirements.returningcCstS)zZTarget platform supports the syntax "(x, y) IN ((x1, y1), (x2, y2), ...)" rrr r rtuple_inszSuiteRequirements.tuple_incCs|jS)z%Target platform tuple IN w/ empty set)rQrr r rtuple_in_w_emptysz"SuiteRequirements.tuple_in_w_emptycCstS)zwtarget platform supports a SELECT statement that has the same name repeated more than once in the columns list.rrr r r%duplicate_names_in_cursor_descriptionsz7SuiteRequirements.duplicate_names_in_cursor_descriptioncCstdddS)z[Target database must have 'denormalized', i.e. UPPERCASE as case insensitive names.cSs |jjj Sr)r&rCZrequires_name_normalizer(r r rr!rDz6SuiteRequirements.denormalized_names..z,Backend does not require denormalized names.rErr r rdenormalized_namessz$SuiteRequirements.denormalized_namescCstdddS)zTtarget database must support multiple VALUES clauses in an INSERT statement.cSs |jjj Sr)r&rCZsupports_multivalues_insertr(r r rr!rDz7SuiteRequirements.multivalues_inserts..z*Backend does not support multirow inserts.rErr r rmultivalues_insertssz%SuiteRequirements.multivalues_insertscCstS)zvtarget dialect implements the executioncontext.get_lastrowid() method without reliance on RETURNING. rrr r rimplements_get_lastrowidsz*SuiteRequirements.implements_get_lastrowidcCstS)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. rrr r remulated_lastrowids z$SuiteRequirements.emulated_lastrowidcCstS)ztarget dialect retrieves cursor.lastrowid or an equivalent after an insert() construct executes, even if the table has a Sequence on it. rrr r r&emulated_lastrowid_even_with_sequencessz8SuiteRequirements.emulated_lastrowid_even_with_sequencescCstS)z]target platform includes a 'lastrowid' accessor on the DBAPI cursor object. rrr r rdbapi_lastrowidsz!SuiteRequirements.dbapi_lastrowidcCstS)z#Target database must support VIEWs.rrr r rviewsszSuiteRequirements.viewscCs tddS)zXTarget database must support external schemas, and have one named 'test_schema'.cSs |jjjSr)r&rCZsupports_schemasr(r r rr!rDz+SuiteRequirements.schemas..rrr r rschemasszSuiteRequirements.schemascCstS)zJtarget system must support reflection of inter-schema foreign keysrrr r rcross_schema_fk_reflectionsz,SuiteRequirements.cross_schema_fk_reflectioncCstS)aTarget supports refleciton of FOREIGN KEY constraints and will return the name of the constraint that was used in the "CONSTRANT FOREIGN KEY" DDL. MySQL prior to version 8 and MariaDB prior to version 10.5 don't support this. rrr r r&foreign_key_constraint_name_reflections z8SuiteRequirements.foreign_key_constraint_name_reflectioncCstS)ztarget system has a strong concept of 'default' schema that can be referred to implicitly. basically, PostgreSQL. rrr r rimplicit_default_schemasz)SuiteRequirements.implicit_default_schemacCstS)z`target dialect implements provisioning module including set_default_schema_on_connectionrrr r rdefault_schema_name_switchsz,SuiteRequirements.default_schema_name_switchcCstddgdS)z0Target dialect must support server side cursors.cSs |jjjSr)r&rCZsupports_server_side_cursorsr(r r rr!rDz7SuiteRequirements.server_side_cursors..zno server side cursors supportr"rr r rserver_side_cursors sz%SuiteRequirements.server_side_cursorscCstddgdS)z'Target database must support SEQUENCEs.cSs |jjjSr)r&rCsupports_sequencesr(r r rr!rDz-SuiteRequirements.sequences..zno sequence supportr"rr r r sequencesszSuiteRequirements.sequencescCs t|jS)zJthe opposite of "sequences", DB does not support sequences at all.)rZ NotPredicaterbrr r r no_sequencesszSuiteRequirements.no_sequencescCstddgdS)zgTarget database supports sequences, but also optionally as a means of generating new PK values.cSs|jjjo|jjjSr)r&rCrasequences_optionalr(r r rr!*s z6SuiteRequirements.sequences_optional..z.no sequence support, or sequences not optionalr"rr r rrd#s z$SuiteRequirements.sequences_optionalcCstddgS)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. cSs |jjjSrr&rCZpostfetch_lastrowidr(r r rr!:rDz6SuiteRequirements.supports_lastrowid..r"rr r rsupports_lastrowid0s z$SuiteRequirements.supports_lastrowidcCstddgS)z"the opposite of supports_lastrowidcSs |jjj Srrer(r r rr!ArDz8SuiteRequirements.no_lastrowid_support..r"rr r rno_lastrowid_support=sz&SuiteRequirements.no_lastrowid_supportcCstSrrrr r rreflects_pk_namesDsz#SuiteRequirements.reflects_pk_namescCstSrrrr r rtable_reflectionHsz"SuiteRequirements.table_reflectioncCstSrrrr r rcomment_reflectionLsz$SuiteRequirements.comment_reflectioncCs|jS)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. rZrr r rview_column_reflectionPsz(SuiteRequirements.view_column_reflectioncCs|jS)zStarget database must support inspection of the full CREATE VIEW definition.rkrr r rview_reflectionZsz!SuiteRequirements.view_reflectioncCs|jSr)r[rr r rschema_reflection`sz#SuiteRequirements.schema_reflectioncCstSrrrr r r!primary_key_constraint_reflectiondsz3SuiteRequirements.primary_key_constraint_reflectioncCstSrrrr r r!foreign_key_constraint_reflectionhsz3SuiteRequirements.foreign_key_constraint_reflectioncCstSrrrr r r1foreign_key_constraint_option_reflection_ondeletelszCSuiteRequirements.foreign_key_constraint_option_reflection_ondeletecCstSrrrr r r1fk_constraint_option_reflection_ondelete_restrictpszCSuiteRequirements.fk_constraint_option_reflection_ondelete_restrictcCstSrrrr r r1fk_constraint_option_reflection_ondelete_noactiontszCSuiteRequirements.fk_constraint_option_reflection_ondelete_noactioncCstSrrrr r r1foreign_key_constraint_option_reflection_onupdatexszCSuiteRequirements.foreign_key_constraint_option_reflection_onupdatecCstSrrrr r r1fk_constraint_option_reflection_onupdate_restrict|szCSuiteRequirements.fk_constraint_option_reflection_onupdate_restrictcCstSrrrr r rtemp_table_reflectionsz'SuiteRequirements.temp_table_reflectioncCs|jSr)rvrr r rtemp_table_reflect_indexessz,SuiteRequirements.temp_table_reflect_indexescCstS)z8target dialect supports listing of temporary table namesrrr r rtemp_table_namessz"SuiteRequirements.temp_table_namescCstS)z)target database supports temporary tablesrrr r rtemporary_tablessz"SuiteRequirements.temporary_tablescCstS)z(target database supports temporary viewsrrr r rtemporary_viewssz!SuiteRequirements.temporary_viewscCstSrrrr r rindex_reflectionsz"SuiteRequirements.index_reflectioncCstSrrrr r rindex_reflects_included_columnssz1SuiteRequirements.index_reflects_included_columnscCstS)z?target database supports CREATE INDEX with per-column ASC/DESC.rrr r rindexes_with_ascdescsz&SuiteRequirements.indexes_with_ascdesccCstS)z>target database supports CREATE INDEX against SQL expressions.rrr r rindexes_with_expressionssz*SuiteRequirements.indexes_with_expressionscCstS)z8target dialect supports reflection of unique constraintsrrr r runique_constraint_reflectionsz.SuiteRequirements.unique_constraint_reflectioncCstS)z7target dialect supports reflection of check constraintsrrr r rcheck_constraint_reflectionsz-SuiteRequirements.check_constraint_reflectioncCstS)ztarget dialect raises IntegrityError when reporting an INSERT with a primary key violation. (hint: it should) rrr r r$duplicate_key_raises_integrity_errorsz6SuiteRequirements.duplicate_key_raises_integrity_errorcCstS)z3Target database must support VARCHAR with no lengthrrr r runbounded_varcharsz#SuiteRequirements.unbounded_varcharcCstS)zTarget database/dialect must support Python unicode objects with non-ASCII characters represented, delivered as bound parameters as well as in result rows. rrr r r unicode_dataszSuiteRequirements.unicode_datacCstS)zRTarget driver must support some degree of non-ascii symbol names. rrr r r unicode_ddlszSuiteRequirements.unicode_ddlcCstS)z?Target driver can create tables with a name like 'some " table'rrr r rsymbol_names_w_double_quotesz-SuiteRequirements.symbol_names_w_double_quotecCstS)ztarget dialect supports rendering of a date, time, or datetime as a literal string, e.g. via the TypeEngine.literal_processor() method. rrr r rdatetime_literalssz#SuiteRequirements.datetime_literalscCstS)zUtarget dialect supports representation of Python datetime.datetime() objects.rrr r rdatetimeszSuiteRequirements.datetimecCstS)zftarget dialect supports representation of Python datetime.datetime() with microsecond objects.rrr r rdatetime_microsecondssz'SuiteRequirements.datetime_microsecondscCstS)ztarget dialect supports representation of Python datetime.datetime() with microsecond objects but only if TIMESTAMP is used.rrr r rtimestamp_microsecondssz(SuiteRequirements.timestamp_microsecondscCstSzutarget dialect supports representation of Python datetime.datetime() objects with historic (pre 1970) values.rrr r rdatetime_historicsz#SuiteRequirements.datetime_historiccCstS)zQtarget dialect supports representation of Python datetime.date() objects.rrr r rdateszSuiteRequirements.datecCstS)zPtarget dialect accepts a datetime object as the target of a date column.rrr r rdate_coerces_from_datetimesz,SuiteRequirements.date_coerces_from_datetimecCstSrrrr r r date_historic szSuiteRequirements.date_historiccCstS)zQtarget dialect supports representation of Python datetime.time() objects.rrr r rtimeszSuiteRequirements.timecCstS)zbtarget dialect supports representation of Python datetime.time() with microsecond objects.rrr r rtime_microsecondssz#SuiteRequirements.time_microsecondscCstS)zttarget database/driver can allow BLOB/BINARY fields to be compared against a bound parameter value. rrr r rbinary_comparisonssz$SuiteRequirements.binary_comparisonscCstS)a!target backend supports simple binary literals, e.g. an expression like:: 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. rrr r rbinary_literals&sz!SuiteRequirements.binary_literalscCstS)z:target dialect supports 'AUTOCOMMIT' as an isolation_levelrrr r r autocommit6szSuiteRequirements.autocommitcCstS)ztarget dialect supports general isolation level settings. Note that this requirement, when enabled, also requires that the get_isolation_levels() method be implemented. rrr r risolation_level;sz!SuiteRequirements.isolation_levelcCsdS)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_COMMITED", "supported": [ "SERIALIZABLE", "READ UNCOMMITTED", "READ COMMITTED", "REPEATABLE READ", "AUTOCOMMIT" ] } Nr rr)r r rget_isolation_levelsEsz&SuiteRequirements.get_isolation_levelscCstS)z.target platform implements a native JSON type.rrr r r json_type_szSuiteRequirements.json_typecCs|jS)zNtarget platform supports numeric array indexes within a JSON structure)rrr r rjson_array_indexesesz$SuiteRequirements.json_array_indexescCstSrrrr r r(json_index_supplementary_unicode_elementlsz:SuiteRequirements.json_index_supplementary_unicode_elementcCstS)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. rrr r r!legacy_unconditional_json_extractpsz3SuiteRequirements.legacy_unconditional_json_extractcCstS)zRtarget backend has general support for moderately high-precision numerics.rrr r rprecision_numerics_generalzsz,SuiteRequirements.precision_numerics_generalcCstS)zbtarget backend supports Decimal() objects using E notation to represent very small values.rrr r r"precision_numerics_enotation_smallsz4SuiteRequirements.precision_numerics_enotation_smallcCstS)zbtarget backend supports Decimal() objects using E notation to represent very large values.rrr r r"precision_numerics_enotation_largesz4SuiteRequirements.precision_numerics_enotation_largecCstS)ztarget backend supports values with many digits on both sides, such as 319438950232418390.273596, 87673.594069654243 rrr r r*precision_numerics_many_significant_digitsszsz)SuiteRequirements.order_by_col_from_unioncCstS)atarget backend supports ORDER BY a column label within an expression. Basically this:: 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. rrr r rorder_by_label_with_expressionHs z0SuiteRequirements.order_by_label_with_expressioncsfdd}t|S)Ncs,z|WdStk r&YdSXdS)NFT)get_order_by_collationNotImplementedErrorr(rr rcheckYs  z3SuiteRequirements.order_by_collation..checkrErrr rrorder_by_collationWs z$SuiteRequirements.order_by_collationcCs tdSr)rrr r rrbsz(SuiteRequirements.get_order_by_collationcCstS)zUTarget driver must support non-ASCII characters being passed at all. rrr r runicode_connectionsesz%SuiteRequirements.unicode_connectionscCstS)zTarget driver must raise a DBAPI-level exception, such as InterfaceError, when the underlying connection has been closed and the execute() method is called. rrr r rgraceful_disconnectslsz&SuiteRequirements.graceful_disconnectscCstS)zU Target must support simultaneous, independent database connections. rrr r rindependent_connectionstsz)SuiteRequirements.independent_connectionscCstS)z9Catchall for a large variety of MySQL on Windows failuresrrr r rskip_mysql_on_windows{sz'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. cSs|jjSr)optionsZlow_connectionsr(r r rr!rDz2SuiteRequirements.ad_hoc_engines..rErr r rad_hoc_enginess z SuiteRequirements.ad_hoc_enginescCst|Sr)rrF_running_on_windowsrr r r no_windowsszSuiteRequirements.no_windowscCstjddddS)NcSs tdkS)NWindows)platformsystemr r r rr!rDz7SuiteRequirements._running_on_windows..zrunning on Windows) description)rZLambdaPredicaterr r rrsz%SuiteRequirements._running_on_windowscCs tdS)Ntiming_intensiverZ requires_tagrr r rrsz"SuiteRequirements.timing_intensivecCs tdS)Nmemory_intensiverrr r rrsz"SuiteRequirements.memory_intensivecCstdddS)zMark tests that use threading and mock at the same time - stability issues have been observed with coverage + python 3.3 cSstjo |jjSr)rZpy3kr has_coverager(r r rr!rDz7SuiteRequirements.threading_with_mock..z%Stability issues with coverage + py3krErr r rthreading_with_mocksz%SuiteRequirements.threading_with_mockcCsdd}t|S)NcSs,z tdWntk r"YdSXdSdS)Nzsqlalchemy-stubs.ext.mypyFT __import__ ImportErrorr(r r rrs  z2SuiteRequirements.sqlalchemy2_stubs..checkr"rr r rsqlalchemy2_stubssz#SuiteRequirements.sqlalchemy2_stubscCstdddS)NcSs tjdkSN)sys version_infor r r rr!rDz+SuiteRequirements.python2..z Python version 2.xx is required.rErr r rpython2szSuiteRequirements.python2cCstdddS)NcSs tjdkSrrr r r rr!rDz+SuiteRequirements.python3..z Python version 3.xx is required.rErr r rpython3szSuiteRequirements.python3cCs|jSr)python36rr r rpep520szSuiteRequirements.pep520cCstdddS)NcSs tjdkS)N)rrr r r rr!rDz,SuiteRequirements.python36..z*Python version 3.6 or greater is required.rErr r rrszSuiteRequirements.python36cCstdddS)NcSs tjdkS)N)rrr r r rr!rDz,SuiteRequirements.python37..z*Python version 3.7 or greater is required.rErr r rpython37szSuiteRequirements.python37cCs|jSr)rrr r r dataclassesszSuiteRequirements.dataclassescCstdddS)NcSstjSr)rcpythonr r r rr!rDz+SuiteRequirements.cpython..zcPython interpreter neededr"rr r rrszSuiteRequirements.cpythoncCsdd}t|dS)NcSs,z tdWntk r"YdSXdSdS)NpatchFTrr r r r check_libs  z2SuiteRequirements.patch_library..check_libzpatch library neededr")rrr r r patch_libraryszSuiteRequirements.patch_librarycs ddlmtfdddS)NrpicklecstjrjdkptjdkS)NcPickle)rr)rrr rrr rr rr!sz5SuiteRequirements.non_broken_pickle..z.Needs cPickle+cPython or newer Python 3 pickle)Zsqlalchemy.utilrrr#rr rrnon_broken_pickles   z#SuiteRequirements.non_broken_picklecCs|jS)ztarget platform must remove all cycles unconditionally when gc.collect() is called, as well as clean out unreferenced subclasses. )rrr r rpredictable_gcsz SuiteRequirements.predictable_gccCstdddS)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. cSs|jjSr)rrr(r r rr!rDz/SuiteRequirements.no_coverage..z(Issues observed when coverage is enabledrErr r r no_coverageszSuiteRequirements.no_coveragecCsdSNFr rr r r_has_mysql_on_windows sz'SuiteRequirements._has_mysql_on_windowscCsdSrr rr r r_has_mysql_fully_case_sensitivesz1SuiteRequirements._has_mysql_fully_case_sensitivecstfddS)Ncs Sr) _has_sqliter rr rr!rDz*SuiteRequirements.sqlite..rErr rrsqliteszSuiteRequirements.sqlitecCstdddS)NcSs t Sr)rZhas_compiled_extr r r rr!rDz/SuiteRequirements.cextensions..zC extensions not installedrErr r r cextensionsszSuiteRequirements.cextensionscCs6ddlm}z|dWdStk r0YdSXdS)Nr) create_enginez sqlite://TF)Z sqlalchemyrr)rrr r rrs  zSuiteRequirements._has_sqlitecCstS)z@dialect makes use of await_() to invoke operations on the DBAPI.rrr r r async_dialect$szSuiteRequirements.async_dialectcCstS)zSupports computed columnsrrr r rcomputed_columns*sz"SuiteRequirements.computed_columnscCstS)z/Supports computed columns with `persisted=True`rrr r rcomputed_columns_stored/sz)SuiteRequirements.computed_columns_storedcCstS)z0Supports computed columns with `persisted=False`rrr r rcomputed_columns_virtual4sz*SuiteRequirements.computed_columns_virtualcCstS)zSIf the default persistence is virtual or stored when `persisted` is omittedrrr r r"computed_columns_default_persisted9sz4SuiteRequirements.computed_columns_default_persistedcCstS)zTIf persistence information is returned by the reflection of computed columnsrrr r r"computed_columns_reflect_persisted?sz4SuiteRequirements.computed_columns_reflect_persistedcCstS)z1If a backend supports the DISTINCT ON in a selectrrr r rsupports_distinct_onEsz&SuiteRequirements.supports_distinct_oncCstdddS)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` cSs |jjj Sr)r&rCsupports_is_distinct_fromr(r r rr!VrDz=SuiteRequirements.supports_is_distinct_from..z4driver doesn't support an IS DISTINCT FROM constructrErr r rrJs z+SuiteRequirements.supports_is_distinct_fromcCstS)zKIf a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITYrrr r ridentity_columnsZsz"SuiteRequirements.identity_columnscCstS)zIf a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY with a standard syntax. This is mainly to exclude MSSql. rrr r ridentity_columns_standard`sz+SuiteRequirements.identity_columns_standardcCstS)z+backend supports the regexp_match operator.rrr r r regexp_matchhszSuiteRequirements.regexp_matchcCstS)z-backend supports the regexp_replace operator.rrr r rregexp_replacemsz SuiteRequirements.regexp_replacecCstS)z(backend supports the fetch first clause.rrr r r fetch_firstrszSuiteRequirements.fetch_firstcCstS)z5backend supports the fetch first clause with percent.rrr r r fetch_percentwszSuiteRequirements.fetch_percentcCstS)z2backend supports the fetch first clause with ties.rrr r r fetch_ties|szSuiteRequirements.fetch_tiescCstS)z1backend supports the fetch first without order byrrr r rfetch_no_order_bysz#SuiteRequirements.fetch_no_order_bycCstS)zwbackend supports the offset when using fetch first with percent or ties. basically this is "not mssql" rrr r rfetch_offset_with_optionssz+SuiteRequirements.fetch_offset_with_optionscCstS)zIf autoincrement=True on a column does not require an explicit sequence. This should be false only for oracle. rrr r rautoincrement_without_sequencesz0SuiteRequirements.autoincrement_without_sequenceN)r r r propertyrrrrrrrrrr r$r+r,r-r.r/r0r1r2r3r4r5r6r7r8r9r:r;r<r=r>r?r@rArBrGrIrJrKrLrMrNrOrPrQrRrSrTrUrVrWrXrYrZr[r\r]r^r_r`rbrcrdrfrgrhrirjrlrmrnrorprqrrrsrtrurvrwrxryrzr{r|r}r~rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr r r rrs                                                                                                                                           r) __doc__rrrrrr'robjectr rr r r rs