-hWSrSSKrSSKrSSKJr SSKJr SSKJr SSKJr SS K J r "S S \ 5r "S S \ 5r g)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)asyncio) exclusionsonly_on)util) QueuePoolc\rSrSrSrg) RequirementsN)__name__ __module__ __qualname____firstlineno____static_attributes__rtC:\Users\ROHAN GUPTA\OneDrive\Desktop\mathbuddy-assessment\venv\Lib\site-packages\sqlalchemy/testing/requirements.pyr r srr c \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\Su5rxSvry\Sw5rz\Sx5r{\Sy5r|\Sz5r}\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\S5r\S5r\S5r\S5r\S5r\S5r\S5rSr\S5r\S5r\S5r\S5r\S5r\S5rSr\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\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_exists-  ""rc,[R"5$)z?target platform supports IF NOT EXISTS / IF EXISTS for indexes.r%rs rindex_ddl_if_exists%SuiteRequirements.index_ddl_if_exists3r)rc,[R"5$)z*Target database must support foreign keys.rrs r foreign_keysSuiteRequirements.foreign_keys9r rc,[R"5$)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. r%rs rtable_value_constructor)SuiteRequirements.table_value_constructor?  ""rc,[R"5$)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. rrs rstandard_cursor_sql%SuiteRequirements.standard_cursor_sqlKs$  rc,[R"5$)zItarget database must support ON UPDATE..CASCADE behavior in foreign keys.rrs ron_update_cascade#SuiteRequirements.on_update_cascade_   rc,[R"5$)zOtarget database must *not* support ON UPDATE..CASCADE behavior in foreign keys.r%rs rnon_updating_cascade&SuiteRequirements.non_updating_cascadefr)rc,[R"5$Nr%rs rdeferrable_fks SuiteRequirements.deferrable_fksl  ""rc8^[R"U4Sj5$)Ncj>TRR=(d TRR$r?)r8enabledr@rsr?SuiteRequirements.on_update_or_deferrable_fks..vs*D**22+""**+rronly_ifrs`ron_update_or_deferrable_fks-SuiteRequirements.on_update_or_deferrable_fksps !! +  rc4Sn[R"U5$)z"target database is using QueuePoolcJ[URR[5$r?) isinstancedbpoolr configs rgo(SuiteRequirements.queue_pool..go~sfiinni8 8rrHrrSs r queue_poolSuiteRequirements.queue_poolzs 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_offsetrmrc,[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.nullsorderingr)rc,[R"5$)zwtarget database/driver supports bound parameters as column expressions without being in the context of a typed column. r%rs rstandalone_binds"SuiteRequirements.standalone_binds   ""rc,[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_whereclausermrc,[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.ctesr)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_delete  ""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_dmlrrc,[R"5$)zvtarget platform generates new surrogate integer primary key values when insert() is executed, excluding the pk column.rrs rautoincrement_insert&SuiteRequirements.autoincrement_insert%r:rc,[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_commit,s  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_expression9rxrc2[R"SS5$)NcLURRR(+$r?)rOdialectsupports_sane_rowcountrQs rrF1SuiteRequirements.sane_rowcount..Hsvyy00GGGrz&driver doesn't support 'sane' rowcountrskip_ifrs r sane_rowcountSuiteRequirements.sane_rowcountEs!! G 4  rc2[R"SS5$)NcLURRR(+$r?)rOrsupports_sane_multi_rowcountrQs rrF7SuiteRequirements.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(+$r?)rOr supports_sane_rowcount_returningrQs rrF=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$r?)rOrsupports_empty_insertsupports_default_valuessupports_default_metavaluerQs rrF1SuiteRequirements.empty_inserts..bsI699,,BB<yy  88<yy  ;;.}s699,,;;rz:%(database)s %(does_support)s 'RETURNING of multiple rows'rHrs rr SuiteRequirements.full_returningus!! ; H  rc2[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$r?)rOrinsert_executemany_returningrQs rrF@SuiteRequirements.insert_executemany_returning..s699,,IIrzR%(database)s %(does_support)s 'RETURNING of multiple rows with INSERT executemany'rHrs rr.SuiteRequirements.insert_executemany_returnings!! I 5  rc2[R"SS5$)zrtarget platform supports RETURNING for at least one row. .. seealso:: :attr:`.Requirements.full_returning` cBURRR$r?)rOrimplicit_returningrQs rrF-SuiteRequirements.returning..s699,,??rz9%(database)s %(does_support)s 'RETURNING of a single row'rHrs r returningSuiteRequirements.returnings!! ? G  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_descriptionr:rc2[R"SS5$)zSTarget database must have 'denormalized', i.e. UPPERCASE as case insensitive names.cLURRR(+$r?)rOrrequires_name_normalizerQs rrF6SuiteRequirements.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(+$r?)rOrsupports_multivalues_insertrQs rrF7SuiteRequirements.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_lastrowidrmrc,[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_lastrowidr3rc,[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_sequencesrrc,[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$r?)rOrsupports_schemasrQs rrF+SuiteRequirements.schemas..sfii&7&7&H&Hrrrs rschemasSuiteRequirements.schemass HIIrc,[R"5$)zBtarget system must support reflection of inter-schema foreign keysr%rs rcross_schema_fk_reflection,SuiteRequirements.cross_schema_fk_reflectionr)rc,[R"5$)zTarget supports refleciton 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_reflectionr3rc,[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_switchrrc4[R"S/S5$)z0Target dialect must support server side cursors.cBURRR$r?)rOrsupports_server_side_cursorsrQs rrF7SuiteRequirements.server_side_cursors.. sFII--JJrzno server side cursors supportrHrs rserver_side_cursors%SuiteRequirements.server_side_cursorss !! J K ,  rc4[R"S/S5$)z'Target database must support SEQUENCEs.cBURRR$r?)rOrsupports_sequencesrQs rrF-SuiteRequirements.sequences..)sFII--@@rzno sequence supportrHrs r sequencesSuiteRequirements.sequences$s !! @ 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$r?)rOrrsequences_optionalrQs rrF6SuiteRequirements.sequences_optional..;s1vyy00CC 9II%%88 9rz.no sequence support, or sequences not optionalrHrs rr)$SuiteRequirements.sequences_optional4s& !!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$r?rOrpostfetch_lastrowidrQs rrF6SuiteRequirements.supports_lastrowid..KsFII--AArrHrs rsupports_lastrowid$SuiteRequirements.supports_lastrowidAs!! A B  rc2[R"S/5$)z"the opposite of supports_lastrowidcLURRR(+$r?r.rQs rrF8SuiteRequirements.no_lastrowid_support..Rs 1 1 E EErrHrs rno_lastrowid_support&SuiteRequirements.no_lastrowid_supportNs!! E F  rc,[R"5$r?r%rs rreflects_pk_names#SuiteRequirements.reflects_pk_namesUrBrc,[R"5$)z8target database has general support for table reflectionrrs rtable_reflection"SuiteRequirements.table_reflectionY  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_columns^rrc,[R"5$r?r%rs rcomment_reflection$SuiteRequirements.comment_reflectionerBrcUR$)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. rrs rview_column_reflection(SuiteRequirements.view_column_reflectioniszzrcUR$)zKtarget database must support inspection of the full CREATE VIEW definition.rFrs rview_reflection!SuiteRequirements.view_reflectionsszzrcUR$r?)rrs rschema_reflection#SuiteRequirements.schema_reflectionys ||rc,[R"5$r?rrs r!primary_key_constraint_reflection3SuiteRequirements.primary_key_constraint_reflection}  rc,[R"5$r?rrs r!foreign_key_constraint_reflection3SuiteRequirements.foreign_key_constraint_reflectionrRrc,[R"5$r?r%rs r1foreign_key_constraint_option_reflection_ondeleteCSuiteRequirements.foreign_key_constraint_option_reflection_ondeleterBrc,[R"5$r?r%rs r1fk_constraint_option_reflection_ondelete_restrictCSuiteRequirements.fk_constraint_option_reflection_ondelete_restrictrBrc,[R"5$r?r%rs r1fk_constraint_option_reflection_ondelete_noactionCSuiteRequirements.fk_constraint_option_reflection_ondelete_noactionrBrc,[R"5$r?r%rs r1foreign_key_constraint_option_reflection_onupdateCSuiteRequirements.foreign_key_constraint_option_reflection_onupdaterBrc,[R"5$r?r%rs r1fk_constraint_option_reflection_onupdate_restrictCSuiteRequirements.fk_constraint_option_reflection_onupdate_restrictrBrc,[R"5$r?rrs rtemp_table_reflection'SuiteRequirements.temp_table_reflectionrRrcUR$r?)rfrs 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$r?rrs rindex_reflection"SuiteRequirements.index_reflectionrRrc,[R"5$r?r%rs rindex_reflects_included_columns1SuiteRequirements.index_reflects_included_columnsrBrc,[R"5$)z?target database supports CREATE INDEX with per-column ASC/DESC.rrs rindexes_with_ascdesc&SuiteRequirements.indexes_with_ascdescr>rc,[R"5$)z>target database supports CREATE INDEX against SQL expressions.r%rs rindexes_with_expressions*SuiteRequirements.indexes_with_expressionsrrc,[R"5$)z8target dialect supports reflection of unique constraintsrrs runique_constraint_reflection.SuiteRequirements.unique_constraint_reflectionr>rc,[R"5$)z7target dialect supports reflection of check constraintsr%rs rcheck_constraint_reflection-SuiteRequirements.check_constraint_reflectionrrc,[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_errorrmrc,[R"5$)z3Target database must support VARCHAR with no lengthrrs runbounded_varchar#SuiteRequirements.unbounded_varcharr rc,[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_datartrc,[R"5$)zBTarget driver must support some degree of non-ascii symbol names. r%rs r unicode_ddlSuiteRequirements.unicode_ddlrrc,[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_quoter>rc,[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_literalsrrc,[R"5$)zMtarget dialect supports representation of Python datetime.datetime() objects.rrs rdatetimeSuiteRequirements.datetimer:rc,[R"5$)zntarget dialect supports representation of Python datetime.datetime() with tzinfo with DateTime(timezone=True).r%rs rdatetime_timezone#SuiteRequirements.datetime_timezonerrc,[R"5$)zftarget dialect supports representation of Python datetime.time() with tzinfo with Time(timezone=True).r%rs r time_timezoneSuiteRequirements.time_timezone rrc,[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_boundrtrc,[R"5$)z^target dialect supports representation of Python datetime.datetime() with microsecond objects.rrs rdatetime_microseconds'SuiteRequirements.datetime_microsecondsr:rc,[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_microseconds"rrcUR$)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_bound)s***rc,[R"5$zmtarget dialect supports representation of Python datetime.datetime() objects with historic (pre 1970) values.r%rs rdatetime_historic#SuiteRequirements.datetime_historic3rrc,[R"5$)zItarget dialect supports representation of Python datetime.date() objects.rrs rdateSuiteRequirements.date:r:rc,[R"5$)zHtarget dialect accepts a datetime object as the target of a date column.rrs rdate_coerces_from_datetime,SuiteRequirements.date_coerces_from_datetimeAr:rc,[R"5$rr%rs r date_historicSuiteRequirements.date_historicHrrc,[R"5$)zItarget dialect supports representation of Python datetime.time() objects.rrs rtimeSuiteRequirements.timeOr:rc,[R"5$)zZtarget dialect supports representation of Python datetime.time() with microsecond objects.rrs rtime_microseconds#SuiteRequirements.time_microsecondsVr:rc,[R"5$)zdtarget database/driver can allow BLOB/BINARY fields to be compared against a bound parameter value. rrs rbinary_comparisons$SuiteRequirements.binary_comparisons]rmrc,[R"5$)ztarget 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. rrs rbinary_literals!SuiteRequirements.binary_literalse  rc,[R"5$)z:target dialect supports 'AUTOCOMMIT' as an isolation_levelr%rs r autocommitSuiteRequirements.autocommiturrc,[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_levelzrrcg)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" ] } NrrrRs rget_isolation_levels&SuiteRequirements.get_isolation_levelssrc,[R"5$)z.target platform implements a native JSON type.r%rs r json_typeSuiteRequirements.json_typer)rcUR$)zFtarget platform supports numeric array indexes within a JSON structure)rrs rjson_array_indexes$SuiteRequirements.json_array_indexess ~~rc,[R"5$r?rrs r(json_index_supplementary_unicode_element:SuiteRequirements.json_index_supplementary_unicode_elementrRrc,[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_extractrrc,[R"5$)zJtarget backend has general support for moderately high-precision numerics.rrs rprecision_numerics_general,SuiteRequirements.precision_numerics_generalr 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_smallr)rc,[R"5$)zZtarget backend supports Decimal() objects using E notation to represent very large values.r%rs r"precision_numerics_enotation_large4SuiteRequirements.precision_numerics_enotation_larger)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$)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$)zXtarget database can select an aggregate from a subquery that's also using an aggregate rrs rnested_aggregates#SuiteRequirements.nested_aggregatesrmrc,[R"5$)zRtarget database must support ON DELETE CASCADE on a self-referential foreign key rrs rrecursive_fk_cascade&SuiteRequirements.recursive_fk_cascadermrc,[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$)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_typermrc,[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_coercionr|rc,[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_decimals$rtrc,[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_numeric-  rc,[R"5$)zMTarget database must support an unbounded Text() " "type such as TEXT or CLOBrrs r text_typeSuiteRequirements.text_type7r:rc,[R"5$)zDtarget database can persist/return an empty string with a varchar. rrs rempty_strings_varchar'SuiteRequirements.empty_strings_varchar>rmrc,[R"5$)zJtarget database can persist/return an empty string with an unbounded text.rrs rempty_strings_text$SuiteRequirements.empty_strings_textFr:rc,[R"5$)zMtarget database supports use of an unbounded textual field in a WHERE clause.rrs r"expressions_against_unbounded_text4SuiteRequirements.expressions_against_unbounded_textMr:rc,[R"5$)z;target driver must support the literal statement 'select 1'rrs r selectoneSuiteRequirements.selectoneTr>rc,[R"5$)z(Target database must support savepoints.r%rs r savepointsSuiteRequirements.savepointsYr)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_fromerrc,[R"5$)z=Target must support DELETE FROM..FROM or DELETE..USING syntaxr%rs r delete_fromSuiteRequirements.delete_fromjrrc,[R"5$)abTarget 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:: 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_subqueryorrc,[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_signr)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_namesr3rc,[R"5$)ztarget database supports ordering by a column from a SELECT inside of a UNION E.g. (SELECT id, ...) UNION (SELECT id, ...) ORDER BY id rrs rorder_by_col_from_union)SuiteRequirements.order_by_col_from_unionr rc,[R"5$)ztarget 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. r%rs rorder_by_label_with_expression0SuiteRequirements.order_by_label_with_expressions  ""rc<^U4Sjn[R"U5$)NcJ>TRU5 g![a gf=f)NFT)get_order_by_collationNotImplementedError)rRrs rcheck3SuiteRequirements.order_by_collation..checks+ ++F3&  s  ""rrr9s` rorder_by_collation$SuiteRequirements.order_by_collations !!%((rc[5er?)r8rs rr7(SuiteRequirements.get_order_by_collations !##rc,[R"5$)zETarget driver must support non-ASCII characters being passed at all. rrs runicode_connections%SuiteRequirements.unicode_connectionsr:rc,[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_disconnectsrmrc,[R"5$)zE Target must support simultaneous, independent database connections. rrs rindependent_connections)SuiteRequirements.independent_connectionsr:rc,[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$r?)optionslow_connectionsrQs rrF2SuiteRequirements.ad_hoc_engines..s6>>99rrrs rad_hoc_engines SuiteRequirements.ad_hoc_enginess!! 9  rcJ[R"UR55$r?)rr_running_on_windowsrs r no_windowsSuiteRequirements.no_windowss!!$":":"<==rc.[R"SSS9$)Nc2[R"5S:H$)NWindows)platformsystemrrrrF7SuiteRequirements._running_on_windows..sHOO%2rzrunning on Windows) description)rLambdaPredicaters rrT%SuiteRequirements._running_on_windowss)) 2,  rc.[R"S5$)Ntiming_intensiver requires_tagrs rra"SuiteRequirements.timing_intensive&&'9::rc.[R"S5$)Nmemory_intensiverbrs rrg"SuiteRequirements.memory_intensivererc2[R"SS5$)zzMark tests that use threading and mock at the same time - stability issues have been observed with coverage + python 3.3 c\[R=(a URR$r?)r py3krN has_coveragerQs rrF7SuiteRequirements.threading_with_mock..s499D)D)DDrz%Stability issues with coverage + py3krrs rthreading_with_mock%SuiteRequirements.threading_with_mocks !! D 3  rc4Sn[R"U5$)Nc<[S5 g![a gf=f)Nzsqlalchemy-stubs.ext.mypyTF __import__ ImportErrorrQs rr92SuiteRequirements.sqlalchemy2_stubs..checks) 67    rHr;s rsqlalchemy2_stubs#SuiteRequirements.sqlalchemy2_stubss !!%((rc2[R"SS5$)Nc([RS:$N)sys version_inforrrrF+SuiteRequirements.python2.. sC$$,rz Python version 2.xx is required.rrs rpython2SuiteRequirements.python2 s!! , .  rc2[R"SS5$)Nc([RS:$r{r}rrrrF+SuiteRequirements.python3..sC$$t+rz Python version 3.xx is required.rrs rpython3SuiteRequirements.python3s!! +-O  rcUR$r?)python36rs rpep520SuiteRequirements.pep520 }}rcUR$r?python37rs rinsert_order_dicts$SuiteRequirements.insert_order_dictsrrc2[R"SS5$)Nc([RS:$)N)r|r}rrrrF,SuiteRequirements.python36..!C$$v-rz*Python version 3.6 or greater is required.rrs rrSuiteRequirements.python36!! - 8  rc2[R"SS5$)Nc([RS:$)N)r|r}rrrrF,SuiteRequirements.python37..(rrz*Python version 3.7 or greater is required.rrs rrSuiteRequirements.python37%rrcUR$r?rrs r dataclassesSuiteRequirements.dataclasses,rrc2[R"SS5$)Nc"[R$r?)r py38rrrrF,SuiteRequirements.python38..3sDIIrzPython 3.8 or above requiredrHrs rpython38SuiteRequirements.python380s!! =  rc2[R"SS5$)Nc"[R$r?)r cpythonrrrrF+SuiteRequirements.cpython..9sDLLrzcPython interpreter neededrHrs rrSuiteRequirements.cpython6s!! ">  rc2[R"SS5$)Nc"[R$r?)r is64bitrrrrF+SuiteRequirements.is64bit..>s$,,rz64bit requiredrHrs rrSuiteRequirements.is64bit<s!!"68HIIrc6Sn[R"US5$)Nc<[S5 g![a gf=f)NpatchTFrrrrr check_lib2SuiteRequirements.patch_library..check_libBs( 7#  rvzpatch library neededrH)rrs r patch_librarySuiteRequirements.patch_library@s !!)-CDDrcF^SSKJm [R"U4SjS5$)Nrpicklec>[R=(a TRS:H=(d [RS:$)NcPickle)r|r)r rrr~rrsrrF5SuiteRequirements.non_broken_pickle..Qs2DLL-9,*6)*rz.Needs cPickle+cPython or newer Python 3 pickle)sqlalchemy.utilrrrI)rrs @rnon_broken_pickle#SuiteRequirements.non_broken_pickleLs#*!! * =   rcUR$)ztarget platform must remove all cycles unconditionally when gc.collect() is called, as well as clean out unreferenced subclasses. )rrs rpredictable_gc SuiteRequirements.predictable_gcWs ||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$r?)rNrlrQs rrF/SuiteRequirements.no_coverage..hs6>>66rz(Issues observed when coverage is enabledrrs r no_coverageSuiteRequirements.no_coverage_s!! 6 6  rcgNFrrs r_has_mysql_on_windows'SuiteRequirements._has_mysql_on_windowslrcgrrrs r_has_mysql_fully_case_sensitive1SuiteRequirements._has_mysql_fully_case_sensitiveorrc8^[R"U4Sj5$)Nc.>TR5(+$r?) _has_sqlitersrrF*SuiteRequirements.sqlite..tsd.>.>.@*@rrrs`rsqliteSuiteRequirements.sqliters!!"@AArc2[R"SS5$)Nc6[R"5(+$r?)r has_compiled_extrrrrF/SuiteRequirements.cextensions..ys--//rzC extensions not installedrrs r cextensionsSuiteRequirements.cextensionsvs!! /1M  rcBSSKJn U"S5 g![a gf=f)Nr) create_enginez sqlite://TF) sqlalchemyrrt)rrs rrSuiteRequirements._has_sqlite|s',  + &  s  c,[R"5$)z@dialect makes use of await_() to invoke operations on the DBAPI.r%rs r async_dialectSuiteRequirements.async_dialectr)rcUR$r?)greenletrs rrSuiteRequirements.asynciorrc4Sn[R"U5$)NcZ[R(dgSSKng![a gf=f)NFrT) _test_asyncioENABLE_ASYNCIOrrt)rRrs rrS&SuiteRequirements.greenlet..gos/ //   s  **rHrUs rrSuiteRequirements.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(+$r?)rOrsupports_is_distinct_fromrQs rrF=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_percentrrc,[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_optionsrrc,[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 r:rc0[R"S5$)z=If X[Y] can be implemented with ``__class_getitem__``. py3.7+c"[R$r?)r py37rrrrF3SuiteRequirements.generic_classes..s$))rrHrs rgeneric_classes!SuiteRequirements.generic_classess!!"344rrN)rrrrpropertyrr"r'r+r.r1r5r8r<r@rJrVrYr\r_rbrerhrkrorrrvrzr~rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrrr!r%r)r1r6r9r<r@rCrGrJrMrPrTrWrZr]r`rcrfrirlrorrrurxr{r~rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrrrrr!r$r'r*r-r0r3r<r7rArDrGrJrQrUrTrargrnrwrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrrrrr r#r)rrrrrr s !! !! ## ## !!  # #!!&!! ## ##  &&!! !! !! !! !!!! !!!!!! ! ! ! !## !! ## ## !!######## #### !!  ! ! ! !          "" !!             ##!!     !! # ####### JJ ##  # #####     77           ##!!## ## !!!!##########!!**####!!##!!##!!##!!##!!!! !!## !!##!! ## ## !!!! ## ++## !! !! ## !! !! !! ! !#### 4##  !!##!! ## ## ##??!!(!!!!#### !! ! !!!!!!! !!!! !! !!## ## #### ! !##  # #!! # #))$!! !!!! !!    >> ;;;;   ) )            JJ E E      BB  ##  & &######## ## ##    ## ################ ##!! 55rr)__doc__rZr~rrrrr rPr objectr rrrrr/s; & 6 t5 t5r