,hSrSSKJr SSKrSSKrSSKJr SSKJr SSKJ r SS KJ r SS KJ r SS K J r "S S 5r"SS\5rg)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\rSrSrSrg) Requirements!N)__name__ __module__ __qualname____firstlineno____static_attributes__rW/var/www/auris/envauris/lib/python3.13/site-packages/sqlalchemy/testing/requirements.pyrr!srrc\rSrSr\S5r\S5r\S5r\S5r\S5r \S5r \S5r \S 5r \S 5r \S 5r\S 5r\S 5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r \S5r!\S5r"\S 5r#\S!5r$\S"5r%\S#5r&\S$5r'\S%5r(\S&5r)\S'5r*\S(5r+\S)5r,\S*5r-\S+5r.\S,5r/\S-5r0\S.5r1\S/5r2\S05r3\S15r4\S25r5\S35r6\S45r7\S55r8\S65r9\S75r:\S85r;\S95r<\S:5r=\S;5r>\S<5r?\S=5r@\S>5rA\S?5rB\S@5rC\SA5rD\SB5rE\SC5rF\SD5rG\SE5rH\SF5rI\SG5rJ\SH5rK\SI5rL\SJ5rM\SK5rN\SL5rO\SM5rP\SN5rQ\SO5rR\SP5rS\SQ5rT\SR5rU\SS5rV\ST5rW\SU5rX\SV5rY\SW5rZ\SX5r[\SY5r\\SZ5r]\S[5r^\S\5r_\S]5r`\S^5ra\S_5rb\S`5rc\Sa5rd\Sb5re\Sc5rf\Sd5rg\Se5rh\Sf5ri\Sg5rj\Sh5rk\Si5rl\Sj5rm\Sk5rn\Sl5ro\Sm5rp\Sn5rq\So5rr\Sp5rs\Sq5rt\Sr5ru\Ss5rv\St5rw\Su5rx\Sv5ry\Sw5rz\Sx5r{\Sy5r|\Sz5r}\S{5r~\S|5r\S}5r\S~5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5rSr\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5rSr\S5r\S5r\S5r\S5r\S5r\S5r\S5rSr\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5rSrSr\S5r\S5rSr\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5r\S5rSrg)SuiteRequirements%c,[R"5$)z/target platform can emit basic CreateTable DDL.ropenselfs r create_tableSuiteRequirements.create_table&  rc,[R"5$)z-target platform can emit basic DropTable DDL.rrs r drop_tableSuiteRequirements.drop_table,r#rc,[R"5$)z>target platform supports IF NOT EXISTS / IF EXISTS for tables.rclosedrs rtable_ddl_if_exists%SuiteRequirements.table_ddl_if_exists2  ""rc,[R"5$)z?target platform supports IF NOT EXISTS / IF EXISTS for indexes.r(rs rindex_ddl_if_exists%SuiteRequirements.index_ddl_if_exists8r,rc,[R"5$)z0Return databases that support the UUID datatype.r(rs ruuid_data_type SuiteRequirements.uuid_data_type>r,rc,[R"5$)z*Target database must support foreign keys.rrs r foreign_keysSuiteRequirements.foreign_keysDr#rc,[R"5$)zCTarget database creates an index that's reflected for foreign keys.r(rs rforeign_keys_reflect_as_index/SuiteRequirements.foreign_keys_reflect_as_indexJ   ""rc,[R"5$)z=Target database reflects unique indexes as unique constrains.r(rs r*unique_index_reflect_as_unique_constraintsTRR=(d TRR$rN)rGenabledrOrsr?SuiteRequirements.on_update_or_deferrable_fks..s*D**22+""**+rronly_ifrs`ron_update_or_deferrable_fks-SuiteRequirements.on_update_or_deferrable_fkss !! +  rc4Sn[R"U5$)z"target database is using QueuePoolcJ[URR[5$rN) isinstancedbpoolr configs rgo(SuiteRequirements.queue_pool..gosfiinni8 8rrWr rbs r queue_poolSuiteRequirements.queue_pools 9!!"%%rc,[R"5$)z;Target database must support self-referential foreign keys.rrs rself_referential_foreign_keys/SuiteRequirements.self_referential_foreign_keysr#rc,[R"5$)z=Target database must support the DDL phrases for FOREIGN KEY.rrs rforeign_key_ddl!SuiteRequirements.foreign_key_ddlr#rc,[R"5$)z3target database must support names for constraints.rrs rnamed_constraints#SuiteRequirements.named_constraintsr#rc,[R"5$)z8target database must apply names to unnamed constraints.rrs rimplicitly_named_constraints.SuiteRequirements.implicitly_named_constraintsr#rc,[R"5$)ztarget 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. rrs runusual_column_name_characters0SuiteRequirements.unusual_column_name_characterss  rc,[R"5$)z(Target database must support subqueries.rrs r subqueriesSuiteRequirements.subqueriesr#rc,[R"5$)zBtarget database can render OFFSET, or an equivalent, in a SELECT. rrs roffsetSuiteRequirements.offset   rc,[R"5$)zGtarget database can render LIMIT and/or OFFSET using a bound parameter rrs rbound_limit_offset$SuiteRequirements.bound_limit_offsetr|rc,[R"5$)ztarget database can render LIMIT and/or OFFSET with a complete SQL expression, such as one that uses the addition operator. parameter rrs rsql_expression_limit_offset-SuiteRequirements.sql_expression_limit_offset  rc,[R"5$)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. rrs r/parens_in_union_contained_select_w_limit_offsetASuiteRequirements.parens_in_union_contained_select_w_limit_offset  rc,[R"5$)a<Target 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. rrs r0parens_in_union_contained_select_wo_limit_offsetBSuiteRequirements.parens_in_union_contained_select_wo_limit_offset  rc,[R"5$)z;Target database must support boolean expressions as columnsr(rs rboolean_col_expressions)SuiteRequirements.boolean_col_expressionsr,rc,[R"5$)z5Target database allows boolean columns to store NULL.rrs rnullable_booleans#SuiteRequirements.nullable_booleansr#rc,[R"5$)z,Target backends that support nulls ordering.r(rs r nullsorderingSuiteRequirements.nullsordering r,rc,[R"5$)zwtarget database/driver supports bound parameters as column expressions without being in the context of a typed column. rrs rstandalone_binds"SuiteRequirements.standalone_bindsrIrc,[R"5$)zytarget database/driver supports bound parameters with NULL in the WHERE clause, in situations where it has to be typed. rrs r!standalone_null_binds_whereclause3SuiteRequirements.standalone_null_binds_whereclauser|rc,[R"5$)z5Target database must support INTERSECT or equivalent.r(rs r intersectSuiteRequirements.intersect   ""rc,[R"5$)z?Target database must support EXCEPT or equivalent (i.e. MINUS).r(rs rexcept_SuiteRequirements.except_%rrc,[R"5$)z.Target database must support window functions.r(rs rwindow_functions"SuiteRequirements.window_functions*rrc,[R"5$)zTarget database supports CTEsr(rs rctesSuiteRequirements.ctes/r,rc,[R"5$)ztarget database supports CTES that ride on top of a normal UPDATE or DELETE statement which refers to the CTE in a correlated subquery. r(rs rctes_with_update_delete)SuiteRequirements.ctes_with_update_delete5  ""rc,[R"5$)zutarget database supports CTES which consist of INSERT, UPDATE or DELETE *within* the CTE, e.g. WITH x AS (UPDATE....)r(rs r ctes_on_dmlSuiteRequirements.ctes_on_dml>r9rc,[R"5$)zvtarget platform generates new surrogate integer primary key values when insert() is executed, excluding the pk column.rrs rautoincrement_insert&SuiteRequirements.autoincrement_insertErIrc,[R"5$)ztarget 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. rrs rfetch_rows_post_commit(SuiteRequirements.fetch_rows_post_commitLs  rc,[R"5$)zqtarget platform supports SQL expressions in GROUP BY e.g. SELECT x + y AS somelabel FROM table GROUP BY x + y rrs rgroup_by_complex_expression-SuiteRequirements.group_by_complex_expressionYrrc2[R"SS5$)NcLURRR(+$rN)r^dialectsupports_sane_rowcountr`s rrU1SuiteRequirements.sane_rowcount..hsvyy00GGGrz&driver doesn't support 'sane' rowcountrskip_ifrs r sane_rowcountSuiteRequirements.sane_rowcountes!! G 4  rc2[R"SS5$)NcLURRR(+$rN)r^rsupports_sane_multi_rowcountr`s rrU7SuiteRequirements.sane_multi_rowcount..osvyy00MMMrz;driver %(driver)s %(doesnt_support)s 'sane' multi row countrfails_ifrs rsane_multi_rowcount%SuiteRequirements.sane_multi_rowcountls"" M I  rc2[R"SS5$)NcLURRR(+$rN)r^r supports_sane_rowcount_returningr`s rrU=SuiteRequirements.sane_rowcount_w_returning..vs !!BBrz;driver doesn't support 'sane' rowcount when returning is onrrs rsane_rowcount_w_returning+SuiteRequirements.sane_rowcount_w_returningss ""  J   rc2[R"SS5$)zYtarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent.cURRR=(dG URRR=(d URRR$rN)r^rsupports_empty_insertsupports_default_valuessupports_default_metavaluer`s rrU1SuiteRequirements.empty_inserts..sI699,,BB<yy  88<yy  ;;.699,,==rz4%(database)s %(does_support)s 'DELETE ... RETURNING'rWrs rr"SuiteRequirements.delete_returning!! = B  rc2[R"SS5$)z.target platform supports INSERT ... RETURNING.cBURRR$rN)r^rinsert_returningr`s rrU4SuiteRequirements.insert_returning..rrz4%(database)s %(does_support)s 'INSERT ... RETURNING'rWrs rr"SuiteRequirements.insert_returningrrc2[R"SS5$)z.target platform supports UPDATE ... RETURNING.cBURRR$rN)r^rupdate_returningr`s rrU4SuiteRequirements.update_returning..rrz4%(database)s %(does_support)s 'UPDATE ... RETURNING'rWrs rr"SuiteRequirements.update_returningrrc2[R"SS5$)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. cBURRR$rN)r^rinsert_executemany_returningr`s rrU@SuiteRequirements.insert_executemany_returning..s699,,IIrzR%(database)s %(does_support)s 'RETURNING of multiple rows with INSERT executemany'rWrs rr.SuiteRequirements.insert_executemany_returnings!! I 5  rc2[R"SS5$)NcURRR=(aG URRR=(a URRR$rN)r^rsupports_multivalues_insertruse_insertmanyvaluesr`s rrU4SuiteRequirements.insertmanyvalues..sI699,,HH7 !!227 !!667rz=%(database)s %(does_support)s 'insertmanyvalues functionalityrWrs rinsertmanyvalues"SuiteRequirements.insertmanyvaluess !! 7 L   rc,[R"5$)zJTarget platform supports the syntax "(x, y) IN ((x1, y1), (x2, y2), ...)" r(rs rtuple_inSuiteRequirements.tuple_in   ""rcUR$)z%Target platform tuple IN w/ empty set)rrs rtuple_in_w_empty"SuiteRequirements.tuple_in_w_emptys}}rc,[R"5$)zotarget platform supports a SELECT statement that has the same name repeated more than once in the columns list.rrs r%duplicate_names_in_cursor_description7SuiteRequirements.duplicate_names_in_cursor_descriptionrIrc2[R"SS5$)zSTarget database must have 'denormalized', i.e. UPPERCASE as case insensitive names.cLURRR(+$rN)r^rrequires_name_normalizer`s rrU6SuiteRequirements.denormalized_names..svyy00HHHrz,Backend does not require denormalized names.rrs rdenormalized_names$SuiteRequirements.denormalized_namess !! H :  rc2[R"SS5$)zLtarget database must support multiple VALUES clauses in an INSERT statement.cLURRR(+$rN)r^rrr`s rrU7SuiteRequirements.multivalues_inserts..svyy00LLLrz*Backend does not support multirow inserts.rrs rmultivalues_inserts%SuiteRequirements.multivalues_insertss !! L 8  rc,[R"5$)zftarget dialect implements the executioncontext.get_lastrowid() method without reliance on RETURNING. rrs rimplements_get_lastrowid*SuiteRequirements.implements_get_lastrowidr|rc,[R"5$)zDdialect includes the required pep-249 attribute ``cursor.arraysize``rrs r arraysizeSuiteRequirements.arraysizerIrc,[R"5$)atarget 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. r(rs remulated_lastrowid$SuiteRequirements.emulated_lastrowid  ""rc,[R"5$)ztarget dialect retrieves cursor.lastrowid or an equivalent after an insert() construct executes, even if the table has a Sequence on it. r(rs r&emulated_lastrowid_even_with_sequences8SuiteRequirements.emulated_lastrowid_even_with_sequences rrc,[R"5$)zMtarget platform includes a 'lastrowid' accessor on the DBAPI cursor object. r(rs rdbapi_lastrowid!SuiteRequirements.dbapi_lastrowidrrc,[R"5$)z#Target database must support VIEWs.r(rs rviewsSuiteRequirements.viewsr,rc[S5$)zPTarget database must support external schemas, and have one named 'test_schema'.cBURRR$rN)r^rsupports_schemasr`s rrU+SuiteRequirements.schemas..&sfii&7&7&H&Hrrrs rschemasSuiteRequirements.schemas!s HIIrc,[R"5$)zBtarget system must support reflection of inter-schema foreign keysr(rs rcross_schema_fk_reflection,SuiteRequirements.cross_schema_fk_reflection(r,rc,[R"5$)zTarget 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. r(rs r&foreign_key_constraint_name_reflection8SuiteRequirements.foreign_key_constraint_name_reflection.rrc,[R"5$)zttarget system has a strong concept of 'default' schema that can be referred to implicitly. basically, PostgreSQL. r(rs rimplicit_default_schema)SuiteRequirements.implicit_default_schema:  ""rc,[R"5$)zXtarget dialect implements provisioning module including set_default_schema_on_connectionr(rs rdefault_schema_name_switch,SuiteRequirements.default_schema_name_switchDr9rc4[R"S/S5$)z0Target dialect must support server side cursors.cBURRR$rN)r^rsupports_server_side_cursorsr`s rrU7SuiteRequirements.server_side_cursors..PsFII--JJrzno server side cursors supportrWrs rserver_side_cursors%SuiteRequirements.server_side_cursorsKs !! J K ,  rc4[R"S/S5$)z'Target database must support SEQUENCEs.cBURRR$rN)r^rsupports_sequencesr`s rrU-SuiteRequirements.sequences..YsFII--@@rzno sequence supportrWrs r sequencesSuiteRequirements.sequencesTs !! @ A !  rcB[R"UR5$)zBthe opposite of "sequences", DB does not support sequences at all.)r NotPredicater?rs r no_sequencesSuiteRequirements.no_sequences]s &&t~~66rc4[R"S/S5$)z_Target database supports sequences, but also optionally as a means of generating new PK values.cURRR=(a URRR$rN)r^rr=sequences_optionalr`s rrU6SuiteRequirements.sequences_optional..ks1vyy00CC 9II%%88 9rz.no sequence support, or sequences not optionalrWrs rrG$SuiteRequirements.sequences_optionalds& !!9  =   rc2[R"S/5$)ztarget 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. cBURRR$rNr^rpostfetch_lastrowidr`s rrU6SuiteRequirements.supports_lastrowid..{sFII--AArrWrs rsupports_lastrowid$SuiteRequirements.supports_lastrowidqs!! A B  rc2[R"S/5$)z"the opposite of supports_lastrowidcLURRR(+$rNrLr`s rrU8SuiteRequirements.no_lastrowid_support..s 1 1 E EErrWrs rno_lastrowid_support&SuiteRequirements.no_lastrowid_support~s!! E F  rc,[R"5$rNr(rs rreflects_pk_names#SuiteRequirements.reflects_pk_namesrQrc,[R"5$)z8target database has general support for table reflectionrrs rtable_reflection"SuiteRequirements.table_reflection  rc,[R"5$)z|target database supports creation and reflection of tables with no columns, or at least tables that seem to have no columns.r(rs rreflect_tables_no_columns+SuiteRequirements.reflect_tables_no_columnsr9rc,[R"5$)z:Indicates if the database support table comment reflectionr(rs rcomment_reflection$SuiteRequirements.comment_reflectionrrc,[R"5$)zkIndicates if the database support table comment reflection in the full unicode range, including emoji etc. r(rs rcomment_reflection_full_unicode1SuiteRequirements.comment_reflection_full_unicoder9rc,[R"5$)zNindicates if the database support comments on constraints and their reflectionr(rs rconstraint_comment_reflection/SuiteRequirements.constraint_comment_reflectionr,rcUR$)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. r rs rview_column_reflection(SuiteRequirements.view_column_reflectionszzrcUR$)zKtarget database must support inspection of the full CREATE VIEW definition.rjrs rview_reflection!SuiteRequirements.view_reflectionszzrcUR$rN)r&rs rschema_reflection#SuiteRequirements.schema_reflections ||rc,[R"5$)zYtarget database supports schema create and dropped with 'CREATE SCHEMA' and 'DROP SCHEMA'r(rs rschema_create_delete&SuiteRequirements.schema_create_deleter,rc,[R"5$rNrrs r!primary_key_constraint_reflection3SuiteRequirements.primary_key_constraint_reflection  rc,[R"5$rNrrs r!foreign_key_constraint_reflection3SuiteRequirements.foreign_key_constraint_reflectionryrc,[R"5$rNr(rs r1foreign_key_constraint_option_reflection_ondeleteCSuiteRequirements.foreign_key_constraint_option_reflection_ondeleterQrc,[R"5$rNr(rs r1fk_constraint_option_reflection_ondelete_restrictCSuiteRequirements.fk_constraint_option_reflection_ondelete_restrictrQrc,[R"5$rNr(rs r1fk_constraint_option_reflection_ondelete_noactionCSuiteRequirements.fk_constraint_option_reflection_ondelete_noactionrQrc,[R"5$rNr(rs r1foreign_key_constraint_option_reflection_onupdateCSuiteRequirements.foreign_key_constraint_option_reflection_onupdaterQrc,[R"5$rNr(rs r1fk_constraint_option_reflection_onupdate_restrictCSuiteRequirements.fk_constraint_option_reflection_onupdate_restrictrQrc,[R"5$rNrrs rtemp_table_reflection'SuiteRequirements.temp_table_reflectionryrcUR$rN)rrs rtemp_table_reflect_indexes,SuiteRequirements.temp_table_reflect_indexess)))rc,[R"5$)z8target dialect supports listing of temporary table namesr(rs rtemp_table_names"SuiteRequirements.temp_table_namesrrc,[R"5$)z9target dialect supports checking a single temp table namer(rs rhas_temp_table SuiteRequirements.has_temp_tablerrc,[R"5$)z)target database supports temporary tablesrrs rtemporary_tables"SuiteRequirements.temporary_tablesr\rc,[R"5$)z(target database supports temporary viewsr(rs rtemporary_views!SuiteRequirements.temporary_viewsrrc,[R"5$rNrrs rindex_reflection"SuiteRequirements.index_reflectionryrc,[R"5$rNr(rs rindex_reflects_included_columns1SuiteRequirements.index_reflects_included_columnsrQrc,[R"5$)z?target database supports CREATE INDEX with per-column ASC/DESC.rrs rindexes_with_ascdesc&SuiteRequirements.indexes_with_ascdescr\rc,[R"5$)zCtarget database supports reflecting INDEX with per-column ASC/DESC.rrs rreflect_indexes_with_ascdesc.SuiteRequirements.reflect_indexes_with_ascdescr#rc,[R"5$)zrtarget database supports reflecting INDEX with per-column ASC/DESC but reflects them as expressions (like oracle).r(rs r*reflect_indexes_with_ascdesc_as_expressiontarget database supports CREATE INDEX against SQL expressions.r(rs rindexes_with_expressions*SuiteRequirements.indexes_with_expressionsrrc,[R"5$)zDtarget database supports reflection of indexes with SQL expressions.r(rs r reflect_indexes_with_expressions2SuiteRequirements.reflect_indexes_with_expressionsr,rc,[R"5$)z8target dialect supports reflection of unique constraintsrrs runique_constraint_reflection.SuiteRequirements.unique_constraint_reflectionr\rc,[R"5$)z>target dialect supports reflection of inline check constraintsr(rs r"inline_check_constraint_reflection4SuiteRequirements.inline_check_constraint_reflection"rrc,[R"5$)z7target dialect supports reflection of check constraintsr(rs rcheck_constraint_reflection-SuiteRequirements.check_constraint_reflection'rrc,[R"5$)zptarget dialect raises IntegrityError when reporting an INSERT with a primary key violation. (hint: it should) rrs r$duplicate_key_raises_integrity_error6SuiteRequirements.duplicate_key_raises_integrity_error,r|rc,[R"5$)z3Target database must support VARCHAR with no lengthrrs runbounded_varchar#SuiteRequirements.unbounded_varchar4r#rc,[R"5$)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. rrs runicode_data_no_special_types/SuiteRequirements.unicode_data_no_special_types:rrc,[R"5$)zTarget database/dialect must support Python unicode objects with non-ASCII characters represented, delivered as bound parameters as well as in result rows. rrs r unicode_dataSuiteRequirements.unicode_dataCrrc,[R"5$)zBTarget driver must support some degree of non-ascii symbol names. r(rs r unicode_ddlSuiteRequirements.unicode_ddlLr9rc,[R"5$)z?Target driver can create tables with a name like 'some " table'rrs rsymbol_names_w_double_quote-SuiteRequirements.symbol_names_w_double_quoteSr\rc,[R"5$)ztarget dialect supports rendering of a datetime.timedelta as a literal string, e.g. via the TypeEngine.literal_processor() method. r(rs rdatetime_interval#SuiteRequirements.datetime_intervalXrrc,[R"5$)ztarget dialect supports rendering of a date, time, or datetime as a literal string, e.g. via the TypeEngine.literal_processor() method. r(rs rdatetime_literals#SuiteRequirements.datetime_literals`rrc,[R"5$)zMtarget dialect supports representation of Python datetime.datetime() objects.rrs rdatetimeSuiteRequirements.datetimeirIrc,[R"5$)zntarget dialect supports representation of Python datetime.datetime() with tzinfo with DateTime(timezone=True).r(rs rdatetime_timezone#SuiteRequirements.datetime_timezonepr9rc,[R"5$)zftarget dialect supports representation of Python datetime.time() with tzinfo with Time(timezone=True).r(rs r time_timezoneSuiteRequirements.time_timezonewr9rc,[R"5$)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. rrs rdate_implicit_bound%SuiteRequirements.date_implicit_bound~rrc,[R"5$)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. rrs rtime_implicit_bound%SuiteRequirements.time_implicit_boundrrc,[R"5$)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. rrs rdatetime_implicit_bound)SuiteRequirements.datetime_implicit_boundrrc,[R"5$)z^target dialect supports representation of Python datetime.datetime() with microsecond objects.rrs rdatetime_microseconds'SuiteRequirements.datetime_microsecondsrIrc,[R"5$)z|target dialect supports representation of Python datetime.datetime() with microsecond objects but only if TIMESTAMP is used.r(rs rtimestamp_microseconds(SuiteRequirements.timestamp_microsecondsr9rcUR$)ztarget 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. )rrs r%timestamp_microseconds_implicit_bound7SuiteRequirements.timestamp_microseconds_implicit_bounds***rc,[R"5$zmtarget dialect supports representation of Python datetime.datetime() objects with historic (pre 1970) values.r(rs rdatetime_historic#SuiteRequirements.datetime_historicr9rc,[R"5$)zItarget dialect supports representation of Python datetime.date() objects.rrs rdateSuiteRequirements.daterIrc,[R"5$)zHtarget dialect accepts a datetime object as the target of a date column.rrs rdate_coerces_from_datetime,SuiteRequirements.date_coerces_from_datetimerIrc,[R"5$rr(rs r date_historicSuiteRequirements.date_historicr9rc,[R"5$)zItarget dialect supports representation of Python datetime.time() objects.rrs rtimeSuiteRequirements.timerIrc,[R"5$)zZtarget dialect supports representation of Python datetime.time() with microsecond objects.rrs rtime_microseconds#SuiteRequirements.time_microsecondsrIrc,[R"5$)zdtarget database/driver can allow BLOB/BINARY fields to be compared against a bound parameter value. rrs rbinary_comparisons$SuiteRequirements.binary_comparisonsr|rc,[R"5$)atarget 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. rrs rbinary_literals!SuiteRequirements.binary_literals   rc,[R"5$)z:target dialect supports 'AUTOCOMMIT' as an isolation_levelr(rs r autocommitSuiteRequirements.autocommitrrc,[R"5$)ztarget dialect supports general isolation level settings. Note that this requirement, when enabled, also requires that the get_isolation_levels() method be implemented. r(rs risolation_level!SuiteRequirements.isolation_levelr1rc.URR5nURRURR 5nURR US.sSSS5 $![a SSS5 gf=f!,(df  g=f)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" ] } )default supportedN)r^connectrget_isolation_level_values connectiondbapi_connectiondefault_isolation_levelNotImplementedError)r raconnrs rget_isolation_levels&SuiteRequirements.get_isolation_levelss2YY   D  LLCCOO44  $||CC!*! '  !   ! s.B/A. B. B8BBB Bc4Sn[R"U5$)zptarget dialect supports the :meth:`_engine.Dialect.get_isolation_level_values` method added in SQLAlchemy 2.0. cURR5nURRURR 5 SSS5 g![ a SSS5 gf=f!,(df  g=f)NTF)r^rrrrrr)rars rrb8SuiteRequirements.get_isolation_level_values..go2sj""$ LL;;88  %$ +! %$ ! %$s.A./A A. A+ A.*A++A.. A<rWrds rr,SuiteRequirements.get_isolation_level_values*s !!"%%rc4Sn[R"U5$)z[test that the dialect allows the 'isolation_level' argument to be handled by DefaultDialectc[URRSS9nURRS:H$! g=f)NzREAD COMMITTED)r F)r r^urlr_on_connect_isolation_level)raes rrbASuiteRequirements.dialect_level_isolation_level_param..goDsC !IIMM3CII99=MM s9=rWrds r#dialect_level_isolation_level_param5SuiteRequirements.dialect_level_isolation_level_param?s !!"%%rc,[R"5$)z.Target platform implements a native ARRAY typer(rs r array_typeSuiteRequirements.array_typeRrrc,[R"5$)z.target platform implements a native JSON type.r(rs r json_typeSuiteRequirements.json_typeWr,rcUR$)zFtarget platform supports numeric array indexes within a JSON structure)r+rs rjson_array_indexes$SuiteRequirements.json_array_indexes]s ~~rc,[R"5$rNrrs r(json_index_supplementary_unicode_element:SuiteRequirements.json_index_supplementary_unicode_elementdryrc,[R"5$)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. r(rs r!legacy_unconditional_json_extract3SuiteRequirements.legacy_unconditional_json_extracthr1rc,[R"5$)zJtarget backend has general support for moderately high-precision numerics.rrs rprecision_numerics_general,SuiteRequirements.precision_numerics_generalrr#rc,[R"5$)zZtarget backend supports Decimal() objects using E notation to represent very small values.r(rs r"precision_numerics_enotation_small4SuiteRequirements.precision_numerics_enotation_smallxr,rc,[R"5$)zZtarget backend supports Decimal() objects using E notation to represent very large values.rrs r"precision_numerics_enotation_large4SuiteRequirements.precision_numerics_enotation_large~r#rc,[R"5$)zvtarget backend supports values with many digits on both sides, such as 319438950232418390.273596, 87673.594069654243 r(rs r*precision_numerics_many_significant_digits>>rc,[R"5$)z8Target backend supports server side defaults for columnsr(rs rserver_defaults!SuiteRequirements.server_defaultsr,rc,[R"5$)zMTarget backend supports server side defaults with SQL expressions for columnsr(rs rexpression_server_defaults,SuiteRequirements.expression_server_defaultsr9rc,[R"5$)ztarget backend will return a selected Decimal as a Decimal, not a string. e.g.:: expr = decimal.Decimal("15.7563") value = e.scalar(select(literal(expr))) assert value == expr See :ticket:`4036` rrs rimplicit_decimal_binds(SuiteRequirements.implicit_decimal_bindss"  rc,[R"5$)atarget backend will return result columns that are explicitly against NUMERIC or similar precision-numeric datatypes (not including FLOAT or INT types) as Python Decimal objects, and not as floats or ints, including when no SQLAlchemy-side typing information is associated with the statement (e.g. such as a raw SQL string). This should be enabled if either the DBAPI itself returns Decimal objects, or if the dialect has set up DBAPI-specific return type handlers such that Decimal objects come back automatically. rrs r#numeric_received_as_decimal_untyped5SuiteRequirements.numeric_received_as_decimal_untypeds  rc,[R"5$)zXtarget database can select an aggregate from a subquery that's also using an aggregate rrs rnested_aggregates#SuiteRequirements.nested_aggregatesr|rc,[R"5$)zRtarget database must support ON DELETE CASCADE on a self-referential foreign key rrs rrecursive_fk_cascade&SuiteRequirements.recursive_fk_cascader|rc,[R"5$)zA precision numeric type will return empty significant digits, i.e. a value such as 10.000 will come back in Decimal form with the .000 maintained.r(rs r-precision_numerics_retains_significant_digits?SuiteRequirements.precision_numerics_retains_significant_digitsrrc,[R"5$)z@The Float type can persist and load float('inf'), float('-inf').r(rs rinfinity_floats!SuiteRequirements.infinity_floatsr,rc,[R"5$rNr(rs r-float_or_double_precision_behaves_generically?SuiteRequirements.float_or_double_precision_behaves_genericallyrQrc,[R"5$)ztarget backend will return native floating point numbers with at least seven decimal places when using the generic Float type. rrs rprecision_generic_float_type.SuiteRequirements.precision_generic_float_typer|rc,[R"5$)ztarget backend will return the exact float value 15.7563 with only four significant digits from this statement: SELECT :param where :param is the Python float 15.7563 i.e. it does not return 15.75629997253418 rrs rliteral_float_coercion(SuiteRequirements.literal_float_coercionrrc,[R"5$)ztarget backend can return a floating-point number with four significant digits (such as 15.7563) accurately (i.e. without FP inaccuracies, such as 15.75629997253418). rrs rfloats_to_four_decimals)SuiteRequirements.floats_to_four_decimalsrrc,[R"5$)ztarget backend doesn't crash when you try to select a NUMERIC value that has a value of NULL. Added to support Pyodbc bug #351. rrs rfetch_null_from_numeric)SuiteRequirements.fetch_null_from_numerics  rc,[R"5$)z*target backend uses Numeric for Float/Dualrrs rfloat_is_numeric"SuiteRequirements.float_is_numericr#rc,[R"5$)zMTarget database must support an unbounded Text() " "type such as TEXT or CLOBrrs r text_typeSuiteRequirements.text_typerIrc,[R"5$)zDtarget database can persist/return an empty string with a varchar. rrs rempty_strings_varchar'SuiteRequirements.empty_strings_varcharr|rc,[R"5$)zJtarget database can persist/return an empty string with an unbounded text.rrs rempty_strings_text$SuiteRequirements.empty_strings_text#rIrc,[R"5$)zMtarget database supports use of an unbounded textual field in a WHERE clause.rrs r"expressions_against_unbounded_text4SuiteRequirements.expressions_against_unbounded_text*rIrc,[R"5$)z;target driver must support the literal statement 'select 1'rrs r selectoneSuiteRequirements.selectone1r\rc,[R"5$)z(Target database must support savepoints.r(rs r savepointsSuiteRequirements.savepoints6r,rc,[R"5$)z4Target database must support two-phase transactions.r(rs rtwo_phase_transactions(SuiteRequirements.two_phase_transactions<r,rc,[R"5$)z'Target must support UPDATE..FROM syntaxr(rs r update_fromSuiteRequirements.update_fromBrrc,[R"5$)z=Target must support DELETE FROM..FROM or DELETE..USING syntaxr(rs r delete_fromSuiteRequirements.delete_fromGrrc,[R"5$)avTarget must support UPDATE (or DELETE) where the same table is present in a subquery in the WHERE clause. This is an ANSI-standard syntax that apparently MySQL can't handle, such as: .. sourcecode:: sql UPDATE documents SET flag=1 WHERE documents.title IN (SELECT max(documents.title) AS title FROM documents GROUP BY documents.user_id ) rrs rupdate_where_target_in_subquery1SuiteRequirements.update_where_target_in_subqueryLrrc,[R"5$)zGtarget database must use a plain percent '%' as the 'modulus' operator.r(rs rmod_operator_as_percent_sign.SuiteRequirements.mod_operator_as_percent_sign^r,rc,[R"5$)ztarget 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. r(rs rpercent_schema_names&SuiteRequirements.percent_schema_namesdrrc,[R"5$)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 rrs rorder_by_col_from_union)SuiteRequirements.order_by_col_from_unionprrc,[R"5$)ztarget 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. r(rs rorder_by_label_with_expression0SuiteRequirements.order_by_label_with_expression~s  ""rc<^U4Sjn[R"U5$)NcJ>TRU5 g![a gf=f)NFT)get_order_by_collationr)rar s rcheck3SuiteRequirements.order_by_collation..checks+ ++F3&  s  ""rr rs` rorder_by_collation$SuiteRequirements.order_by_collations !!%((rc[5erN)rr ras rr(SuiteRequirements.get_order_by_collations !##rc,[R"5$)zETarget driver must support non-ASCII characters being passed at all. rrs runicode_connections%SuiteRequirements.unicode_connectionsrIrc,[R"5$)zTarget driver must raise a DBAPI-level exception, such as InterfaceError, when the underlying connection has been closed and the execute() method is called. rrs rgraceful_disconnects&SuiteRequirements.graceful_disconnectsr|rc,[R"5$)zE Target must support simultaneous, independent database connections. rrs rindependent_connections)SuiteRequirements.independent_connectionsrIrc,[R"5$)zn Target must support simultaneous, independent database connections that will be used in a readonly fashion. rrs r independent_readonly_connections2SuiteRequirements.independent_readonly_connectionsrrc,[R"5$)z9Catchall for a large variety of MySQL on Windows failuresrrs rskip_mysql_on_windows'SuiteRequirements.skip_mysql_on_windowsr\rc0[R"S5$)zTest 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. c.URR$rN)optionslow_connectionsr`s rrU2SuiteRequirements.ad_hoc_engines..s6>>99rrrs rad_hoc_engines SuiteRequirements.ad_hoc_enginess!! 9  rcJ[R"UR55$rN)rr_running_on_windowsrs r no_windowsSuiteRequirements.no_windowss!!$":":"<==rc.[R"SSS9$)Nc2[R"5S:H$)NWindows)platformsystemrrrrU7SuiteRequirements._running_on_windows..sHOO%2rzrunning on Windows) description)rLambdaPredicaters rr%SuiteRequirements._running_on_windowss)) 2,  rc:SSKJn URR$Nrr`)ra add_to_markertiming_intensivers rr"SuiteRequirements.timing_intensive##444rc0[R"S5$)Nc([RS:g$)Nposix)osnamerrrrU)SuiteRequirements.posix..s "''W*.6>>66rzStability issues with coveragerrs rthreading_with_mock%SuiteRequirements.threading_with_mocks !! 6 ,  rc4Sn[R"U5$)Nc<[S5 g![a gf=fNzsqlalchemy-stubs.ext.mypyTF __import__ ImportErrorr`s rr2SuiteRequirements.sqlalchemy2_stubs..check) 67    rWrs rsqlalchemy2_stubs#SuiteRequirements.sqlalchemy2_stubs !!%((rc4Sn[R"U5$)Nc<[S5 g![a gf=frrr`s rr5SuiteRequirements.no_sqlalchemy2_stubs..checkrrrrs rno_sqlalchemy2_stubs&SuiteRequirements.no_sqlalchemy2_stubsrrc4Sn[R"U5$)NcSSKnSSKn[USUR5nUR S5nU"SUR UU4S9n[ U[S5$)Nr TypeAliasTypeTV TA_generic) type_params __value__)typingtyping_extensionsgetattrrTypeVarListhasattrint)rarrrrrs rr:SuiteRequirements.up_to_date_typealias_type..checks^  $#):)H)HM%B&fkk"oB5J:c?K8 8rrWrs rup_to_date_typealias_type+SuiteRequirements.up_to_date_typealias_type s 9!!%((rc2[R"SS5$)Nc"[R$rN)r py38rrrrU,SuiteRequirements.python38..#DIIrzPython 3.8 or above requiredrWrs rpython38SuiteRequirements.python38 !! =  rc2[R"SS5$)Nc"[R$rN)r py39rrrrU,SuiteRequirements.python39..)rrzPython 3.9 or above requiredrWrs rpython39SuiteRequirements.python39&r rc2[R"SS5$)Nc"[R$rN)r py310rrrrU-SuiteRequirements.python310../DJJrzPython 3.10 or above requiredrWrs r python310SuiteRequirements.python310,!!  ?  rc2[R"SS5$)Nc"[R$rN)r py311rrrrU-SuiteRequirements.python311..5rrzPython 3.11 or above requiredrWrs r python311SuiteRequirements.python3112rrc2[R"SS5$)Nc"[R$rN)r py312rrrrU-SuiteRequirements.python312..;rrzPython 3.12 or above requiredrWrs r python312SuiteRequirements.python3128rrc2[R"SS5$)Nc6[RR$rN)r compatpy314b1rrrrU4SuiteRequirements.fail_python314b1..AsDKK''rzFails as of python 3.14.0b1rrs rfail_python314b1"SuiteRequirements.fail_python314b1>s"" ')F  rc2[R"SS5$)zThis requirement is interim to assist with backporting of issue #12405. SQLAlchemy 2.0 still includes the ``await_fallback()`` method that makes use of ``asyncio.get_event_loop_policy()``. This is removed in SQLAlchemy 2.1. c"[R$rN)r py314rrrrU1SuiteRequirements.not_python314..Orrz"Python 3.14 or above not supportedrrs r not_python314SuiteRequirements.not_python314Ds!!  D  rc2[R"SS5$)Nc"[R$rN)r cpythonrrrrU+SuiteRequirements.cpython..UsDLLrzcPython interpreter neededrWrs rr3SuiteRequirements.cpythonRs!! ">  rc2[R"SS5$)Nc"[R$rN)r is64bitrrrrU+SuiteRequirements.is64bit..Zs$,,rz64bit requiredrWrs rr8SuiteRequirements.is64bitXs!!"68HIIrc6Sn[R"US5$)Nc<[S5 g![a gf=f)NpatchTFrrrr check_lib2SuiteRequirements.patch_library..check_lib^s( 7#  rzpatch library neededrW)r r>s r patch_librarySuiteRequirements.patch_library\s !!)-CDDrcUR$)ztarget platform must remove all cycles unconditionally when gc.collect() is called, as well as clean out unreferenced subclasses. )r3rs rpredictable_gc SuiteRequirements.predictable_gchs ||rc2[R"SS5$)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. c.URR$rNrr`s rrU/SuiteRequirements.no_coverage..yrrz(Issues observed when coverage is enabledrrs r no_coverageSuiteRequirements.no_coverageps!! 6 6  rcgNFrrs r_has_mysql_on_windows'SuiteRequirements._has_mysql_on_windows}rcgrKrrs r_has_mysql_fully_case_sensitive1SuiteRequirements._has_mysql_fully_case_sensitiverNrc8^[R"U4Sj5$)Nc.>TR5(+$rN) _has_sqlitersrrU*SuiteRequirements.sqlite..sd.>.>.@*@rrrs`rsqliteSuiteRequirements.sqlites!!"@AArc2[R"SS5$)Nc6[R"5(+$rN)r has_compiled_extrrrrU/SuiteRequirements.cextensions..s--//rzCython extensions not installedrrs r cextensionsSuiteRequirements.cextensionss!! / -  rcBSSKJn U"S5 g![a gf=f)Nrr z sqlite://TF) sqlalchemyr r)r r s rrTSuiteRequirements._has_sqlites',  + &  s  c,[R"5$)z@dialect makes use of await_() to invoke operations on the DBAPI.r(rs r async_dialectSuiteRequirements.async_dialectr,rcUR$rN)greenletrs rrSuiteRequirements.asyncios }}rc4Sn[R"U5$)Nc.SSKng![a gf=f)NrFT)rerrares rrb)SuiteRequirements.no_greenlet..gos#   s  rWrds r no_greenletSuiteRequirements.no_greenlets !!"%%rc4Sn[R"U5$)NcZ[R(dgSSKng![a gf=f)NFrT) _test_asyncioENABLE_ASYNCIOrerris rrb&SuiteRequirements.greenlet..gos/ //   s  **rWrds rreSuiteRequirements.greenlets !!"%%rc,[R"5$)zSupports computed columnsr(rs rcomputed_columns"SuiteRequirements.computed_columnsrrc,[R"5$)z/Supports computed columns with `persisted=True`r(rs rcomputed_columns_stored)SuiteRequirements.computed_columns_storedrrc,[R"5$)z0Supports computed columns with `persisted=False`r(rs rcomputed_columns_virtual*SuiteRequirements.computed_columns_virtualrrc,[R"5$)zKIf the default persistence is virtual or stored when `persisted` is omittedr(rs r"computed_columns_default_persisted4SuiteRequirements.computed_columns_default_persistedr,rc,[R"5$)zLIf persistence information is returned by the reflection of computed columnsr(rs r"computed_columns_reflect_persisted4SuiteRequirements.computed_columns_reflect_persistedr,rc,[R"5$)z1If a backend supports the DISTINCT ON in a selectr(rs rsupports_distinct_on&SuiteRequirements.supports_distinct_onrrc2[R"SS5$)zSupports 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` cLURRR(+$rN)r^rsupports_is_distinct_fromr`s rrU=SuiteRequirements.supports_is_distinct_from..svyy00JJJrz4driver doesn't support an IS DISTINCT FROM constructrrs rr+SuiteRequirements.supports_is_distinct_froms!! J B  rc,[R"5$)zCIf a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITYr(rs ridentity_columns"SuiteRequirements.identity_columnsr,rc,[R"5$)z}If a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY with a standard syntax. This is mainly to exclude MSSql. r(rs ridentity_columns_standard+SuiteRequirements.identity_columns_standardrrc,[R"5$)z+backend supports the regexp_match operator.r(rs r regexp_matchSuiteRequirements.regexp_matchrrc,[R"5$)z-backend supports the regexp_replace operator.r(rs rregexp_replace SuiteRequirements.regexp_replacerrc,[R"5$)z(backend supports the fetch first clause.r(rs r fetch_firstSuiteRequirements.fetch_firstrrc,[R"5$)z5backend supports the fetch first clause with percent.r(rs r fetch_percentSuiteRequirements.fetch_percent rrc,[R"5$)z2backend supports the fetch first clause with ties.r(rs r fetch_tiesSuiteRequirements.fetch_tiesrrc,[R"5$)z1backend supports the fetch first without order byr(rs rfetch_no_order_by#SuiteRequirements.fetch_no_order_byrrc,[R"5$)zgbackend supports the offset when using fetch first with percent or ties. basically this is "not mssql" r(rs rfetch_offset_with_options+SuiteRequirements.fetch_offset_with_optionsr9rc,[R"5$)zbackend supports fetch / offset with expression in them, like SELECT * FROM some_table OFFSET 1 + 1 ROWS FETCH FIRST 1 + 1 ROWS ONLY r(rs rfetch_expression"SuiteRequirements.fetch_expressionrrc,[R"5$)zoIf autoincrement=True on a column does not require an explicit sequence. This should be false only for oracle. rrs rautoincrement_without_sequence0SuiteRequirements.autoincrement_without_sequence(rIrc,[R"5$)z=If X[Y] can be implemented with ``__class_getitem__``. py3.7+rrs rgeneric_classes!SuiteRequirements.generic_classes/r\rc,[R"5$)z@indicates if the json_deserializer function is called with bytesr(rs rjson_deserializer_binary*SuiteRequirements.json_deserializer_binary4rrc,[R"5$)z6Target database must support reflecting table_options.r(rs rreflect_table_options'SuiteRequirements.reflect_table_options9rrc,[R"5$)z0Target database must support MATERIALIZED VIEWs.r(rs rmaterialized_views$SuiteRequirements.materialized_views>rrc,[R"5$)z/Target database reflect MATERIALIZED VIEWs pks.r(rs rmaterialized_views_reflect_pk/SuiteRequirements.materialized_views_reflect_pkCrrc,[R"5$)z#Target database supports bitwise orr(rs rsupports_bitwise_or%SuiteRequirements.supports_bitwise_orHrrc,[R"5$)z$Target database supports bitwise andr(rs rsupports_bitwise_and&SuiteRequirements.supports_bitwise_andMrrc,[R"5$)z$Target database supports bitwise notr(rs rsupports_bitwise_not&SuiteRequirements.supports_bitwise_notRrrc,[R"5$)z$Target database supports bitwise xorr(rs rsupports_bitwise_xor&SuiteRequirements.supports_bitwise_xorWrrc,[R"5$)z4Target database supports bitwise left or right shiftr(rs rsupports_bitwise_shift(SuiteRequirements.supports_bitwise_shift\rrc,[R"5$)zFTarget backend supports custom ESCAPE characters with LIKE comparisonsrrs r like_escapesSuiteRequirements.like_escapesar#rrN)rrrrpropertyr!r%r*r.r1r4r7r;r>rArDrGrKrOrYrerhrkrnrqrtrwrzr~rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrrrr r&r)r,r/r3r9r?rCrGrOrTrWrZr^rardrgrkrnrqrtrwr{r~rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr r rrr%r(r+r.r1r4r7r:r=r@rCrFrIrLrOrRrUrXr[r^rardrgrjrmrprsrvryr|rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr"r)r/r3r8r@rCrHrLrPrVr\rTrbrrkrertrwrzr}rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr%s !! !! ## ## ## !! ## ## ##  # #!!&!! ## ##  &&!! !! !! !! !!!! !!!!!! ! ! ! !## !! ## !! !!######## #### !!  ! ! ! !          "" !!             ##!!     !!!!  # ####### JJ ##  # #####     77           ##!!## #### ##  ## !!!!##########!!**####!!##!!##!!!! ## #### !!####!!!! !!!!## !!####!! ## ## !!!!!!!! ## ++## !! !! ## !! !! !!!!"####$L&&(&&$####  !!##!! ## !! ##??## ## !!$ ! !!!!!#### ##!! ! !!!!!!! !! !!!! !! !!## ## ####!!"##  # # ! !## ))$!! !!!! !!!!    >> 55 >>55    ) ) ) )))(                  JJ E E    BB  ##  & & & &######## ## ##    ## ################ ##!! !!##################!!rr)__doc__ __future__rrrrrrorrr r r_r rrrrrrs?# &  @! @!r