관리-도구
편집 파일: requirements.cpython-38.pyc
U -?�f&� � @ s� d Z ddlmZ ddlZddlmZ ddlmZ ddlmZ dd lm Z dd lm Z dd l m Z G d d � d �Z G dd� de �ZdS )z�Global 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)� exclusions��only_on� �� create_engine)�util)� QueuePoolc @ s e Zd ZdS )� RequirementsN)�__name__� __module__� __qualname__� r r �O/opt/hc_python/lib64/python3.8/site-packages/sqlalchemy/testing/requirements.pyr s r c @ s� e Zd Zedd� �Zedd� �Zedd� �Zedd� �Zed d � �Zed d � �Z ed d� �Z edd� �Z edd� �Z edd� �Z edd� �Zedd� �Zedd� �Zedd � �Zed d � �Zed d � �Zed!d"� �Zed#d$� �Zed%d&� �Zed'd(� �Zed)d*� �Zed+d,� �Zed-d.� �Zed/d0� �Zed1d2� �Z ed3d4� �Z ed5d6� �Z ed7d8� �Z ed9d:� �Z ed;d<� �Z!ed=d>� �Z"ed?d@� �Z#edAdB� �Z$edCdD� �Z%edEdF� �Z&edGdH� �Z'edIdJ� �Z(edKdL� �Z)edMdN� �Z*edOdP� �Z+edQdR� �Z,edSdT� �Z-edUdV� �Z.edWdX� �Z/edYdZ� �Z0ed[d\� �Z1ed]d^� �Z2ed_d`� �Z3edadb� �Z4edcdd� �Z5ededf� �Z6edgdh� �Z7edidj� �Z8edkdl� �Z9edmdn� �Z:edodp� �Z;edqdr� �Z<edsdt� �Z=edudv� �Z>edwdx� �Z?edydz� �Z@ed{d|� �ZAed}d~� �ZBedd�� �ZCed�d�� �ZDed�d�� �ZEed�d�� �ZFed�d�� �ZGed�d�� �ZHed�d�� �ZIed�d�� �ZJed�d�� �ZKed�d�� �ZLed�d�� �ZMed�d�� �ZNed�d�� �ZOed�d�� �ZPed�d�� �ZQed�d�� �ZRed�d�� �ZSed�d�� �ZTed�d�� �ZUed�d�� �ZVed�d�� �ZWed�d�� �ZXed�d�� �ZYed�d�� �ZZed�d�� �Z[ed�d�� �Z\ed�d�� �Z]ed�d�� �Z^ed�d�� �Z_ed�d�� �Z`ed�d�� �Zaed�d�� �Zbed�d�� �Zced�d �Zded�dĄ �Zeed�dƄ �Zfed�dȄ �Zged�dʄ �Zhed�d̄ �Zied�d΄ �Zjed�dЄ �Zked�d҄ �Zled�dԄ �Zmed�dք �Zned�d �Zoed�dڄ �Zped�d܄ �Zqed�dބ �Zred�d� �Zsed�d� �Zted�d� �Zued�d� �Zved�d� �Zwed�d� �Zxed�d� �Zyed�d� �Zzed�d� �Z{ed�d� �Z|ed�d� �Z}ed�d�� �Z~ed�d�� �Zed�d�� �Z�ed�d�� �Z�ed�d�� �Z�ed��d � �Z�e�d�d� �Z�e�d�d� �Z�e�d�d� �Z�e�d�d� �Z�e�d �d � �Z��d �d � Z�e�d �d� �Z�e�d�d� �Z�e�d�d� �Z�e�d�d� �Z�e�d�d� �Z�e�d�d� �Z�e�d�d� �Z�e�d�d � �Z�e�d �d � �Z�e�d �d � �Z�e�d!�d"� �Z�e�d#�d$� �Z�e�d%�d&� �Z�e�d'�d(� �Z�e�d)�d*� �Z�e�d+�d,� �Z�e�d-�d.� �Z�e�d/�d0� �Z�e�d1�d2� �Z�e�d3�d4� �Z�e�d5�d6� �Z�e�d7�d8� �Z�e�d9�d:� �Z�e�d;�d<� �Z�e�d=�d>� �Z�e�d?�d@� �Z�e�dA�dB� �Z�e�dC�dD� �Z�e�dE�dF� �Z�e�dG�dH� �Z�e�dI�dJ� �Z�e�dK�dL� �Z�e�dM�dN� �Z�e�dO�dP� �Z�e�dQ�dR� �Z�e�dS�dT� �Z�e�dU�dV� �Z�e�dW�dX� �Z��dY�dZ� Z�e�d[�d\� �Z�e�d]�d^� �Z�e�d_�d`� �Z�e�da�db� �Z�e�dc�dd� �Z�e�de�df� �Z�e�dg�dh� �Z��di�dj� Z�e�dk�dl� �Z�e�dm�dn� �Z�e�do�dp� �Z�e�dq�dr� �Z�e�ds�dt� �Z�e�du�dv� �Z�e�dw�dx� �Z�e�dy�dz� �Z�e�d{�d|� �Z�e�d}�d~� �Z�e�d�d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Zǐd��d�� ZȐd��d�� Z�e�d��d�� �Z�e�d��d�� �Zːd��d�� Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d�� �Z�e�d��d �Z�e�dÐdĄ �Z�e�dŐdƄ �Z�e�dǐdȄ �Z�e�dɐdʄ �Z�e�dːd̄ �Z�e�d͐d΄ �Z�e�dϐdЄ �Z�e�dѐd҄ �Z�d�S (� �SuiteRequirementsc C s t �� S )z/target platform can emit basic CreateTable DDL.�r �open��selfr r r � create_table% s z SuiteRequirements.create_tablec C s t �� S )z-target platform can emit basic DropTable DDL.r r r r r � drop_table+ s z SuiteRequirements.drop_tablec C s t �� S )z>target platform supports IF NOT EXISTS / IF EXISTS for tables.�r �closedr r r r �table_ddl_if_exists1 s z%SuiteRequirements.table_ddl_if_existsc C s t �� S )z?target platform supports IF NOT EXISTS / IF EXISTS for indexes.r r r r r �index_ddl_if_exists7 s z%SuiteRequirements.index_ddl_if_existsc C s t �� S )z0Return databases that support the UUID datatype.r r r r r �uuid_data_type= s z SuiteRequirements.uuid_data_typec C s t �� S )z*Target database must support foreign keys.r r r r r � foreign_keysC s z SuiteRequirements.foreign_keysc C s t �� S )zKTarget database creates an index that's reflected for foreign keys.r r r r r � foreign_keys_reflect_as_indexI s z/SuiteRequirements.foreign_keys_reflect_as_indexc C s t �� S )z=Target database reflects unique indexes as unique constrains.r r r r r �*unique_index_reflect_as_unique_constraintsP s z<SuiteRequirements.unique_index_reflect_as_unique_constraintsc C s t �� S )z7Target database reflects unique constraints as indexes.r r r r r �#unique_constraints_reflect_as_indexV s z5SuiteRequirements.unique_constraints_reflect_as_indexc C s t �� S )z�Database / 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 r r r r �table_value_constructor\ s z)SuiteRequirements.table_value_constructorc C s t �� S )a� Target 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. r r r r r �standard_cursor_sqlh s z%SuiteRequirements.standard_cursor_sqlc C s t �� S )zQtarget database must support ON UPDATE..CASCADE behavior in foreign keys.r r r r r �on_update_cascade| s z#SuiteRequirements.on_update_cascadec C s t �� S )zWtarget database must *not* support ON UPDATE..CASCADE behavior in foreign keys.r r r r r �non_updating_cascade� s z&SuiteRequirements.non_updating_cascadec C s t �� S �Nr r r r r �deferrable_fks� s z SuiteRequirements.deferrable_fksc s t �� fdd��S )Nc s � j jp� jjS r' )r% �enabledr( r r r r �<lambda>� s z?SuiteRequirements.on_update_or_deferrable_fks.<locals>.<lambda>�r Zonly_ifr r r r �on_update_or_deferrable_fks� s �z-SuiteRequirements.on_update_or_deferrable_fksc C s dd� }t �|�S )z"target database is using QueuePoolc S s t | jjt�S r' )� isinstance�db�poolr ��configr r r �go� s z(SuiteRequirements.queue_pool.<locals>.gor+ �r r2 r r r � queue_pool� s z SuiteRequirements.queue_poolc C s t �� S )z;Target database must support self-referential foreign keys.r r r r r � self_referential_foreign_keys� s z/SuiteRequirements.self_referential_foreign_keysc C s t �� S )z=Target database must support the DDL phrases for FOREIGN KEY.r r r r r �foreign_key_ddl� s z!SuiteRequirements.foreign_key_ddlc C s t �� S )z3target database must support names for constraints.r r r r r �named_constraints� s z#SuiteRequirements.named_constraintsc C s t �� S )z8target database must apply names to unnamed constraints.r r r r r � implicitly_named_constraints� s z.SuiteRequirements.implicitly_named_constraintsc C s t �� S )a target 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. r r r r r � unusual_column_name_characters� s z0SuiteRequirements.unusual_column_name_charactersc C s t �� S )z(Target database must support subqueries.r r r r r � subqueries� s z SuiteRequirements.subqueriesc C s t �� S )zRtarget database can render OFFSET, or an equivalent, in a SELECT. r r r r r �offset� s zSuiteRequirements.offsetc C s t �� S )zWtarget database can render LIMIT and/or OFFSET using a bound parameter r r r r r �bound_limit_offset� s z$SuiteRequirements.bound_limit_offsetc C s t �� S )z�target database can render LIMIT and/or OFFSET with a complete SQL expression, such as one that uses the addition operator. parameter r r r r r �sql_expression_limit_offset� s z-SuiteRequirements.sql_expression_limit_offsetc C s t �� S )z�Target 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. r r r r r �/parens_in_union_contained_select_w_limit_offset� s zASuiteRequirements.parens_in_union_contained_select_w_limit_offsetc C s t �� S )al 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. r r r r r �0parens_in_union_contained_select_wo_limit_offset� s zBSuiteRequirements.parens_in_union_contained_select_wo_limit_offsetc C s t �� S )z;Target database must support boolean expressions as columnsr r r r r �boolean_col_expressions� s z)SuiteRequirements.boolean_col_expressionsc C s t �� S )z5Target database allows boolean columns to store NULL.r r r r r �nullable_booleans s z#SuiteRequirements.nullable_booleansc C s t �� S )z,Target backends that support nulls ordering.r r r r r � nullsordering s z SuiteRequirements.nullsorderingc C s t �� S )z�target database/driver supports bound parameters as column expressions without being in the context of a typed column. r r r r r �standalone_binds s z"SuiteRequirements.standalone_bindsc C s t �� S )z�target database/driver supports bound parameters with NULL in the WHERE clause, in situations where it has to be typed. r r r r r �!standalone_null_binds_whereclause s z3SuiteRequirements.standalone_null_binds_whereclausec C s t �� S )z5Target database must support INTERSECT or equivalent.r r r r r � intersect s zSuiteRequirements.intersectc C s t �� S )z?Target database must support EXCEPT or equivalent (i.e. MINUS).r r r r r �except_" s zSuiteRequirements.except_c C s t �� S )z.Target database must support window functions.r r r r r �window_functions' s z"SuiteRequirements.window_functionsc C s t �� S )z Target database supports CTEsr r r r r �ctes, s zSuiteRequirements.ctesc C s t �� S )z�target database supports CTES that ride on top of a normal UPDATE or DELETE statement which refers to the CTE in a correlated subquery. r r r r r �ctes_with_update_delete2 s z)SuiteRequirements.ctes_with_update_deletec C s t �� S )z}target database supports CTES which consist of INSERT, UPDATE or DELETE *within* the CTE, e.g. WITH x AS (UPDATE....)r r r r r � ctes_on_dml; s z SuiteRequirements.ctes_on_dmlc C s t �� S )z~target platform generates new surrogate integer primary key values when insert() is executed, excluding the pk column.r r r r r �autoincrement_insertB s z&SuiteRequirements.autoincrement_insertc C s t �� S )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. r r r r r �fetch_rows_post_commitI s z(SuiteRequirements.fetch_rows_post_commitc C s t �� S )z�target platform supports SQL expressions in GROUP BY e.g. SELECT x + y AS somelabel FROM table GROUP BY x + y r r r r r �group_by_complex_expressionV s z-SuiteRequirements.group_by_complex_expressionc C s t �dd� d�S )Nc S s | j jj S r' )r. �dialectZsupports_sane_rowcountr0 r r r r* e � z1SuiteRequirements.sane_rowcount.<locals>.<lambda>z&driver doesn't support 'sane' rowcount�r �skip_ifr r r r � sane_rowcountb s �z SuiteRequirements.sane_rowcountc C s t �dd� d�S )Nc S s | j jj S r' )r. rN Z supports_sane_multi_rowcountr0 r r r r* l rO z7SuiteRequirements.sane_multi_rowcount.<locals>.<lambda>z;driver %(driver)s %(doesnt_support)s 'sane' multi row count�r Zfails_ifr r r r �sane_multi_rowcounti s �z%SuiteRequirements.sane_multi_rowcountc C s t �dd� d�S )Nc S s | j jj S r' )r. rN Z supports_sane_rowcount_returningr0 r r r r* s s �z=SuiteRequirements.sane_rowcount_w_returning.<locals>.<lambda>z;driver doesn't support 'sane' rowcount when returning is onrS r r r r �sane_rowcount_w_returningp s �z+SuiteRequirements.sane_rowcount_w_returningc C s t �dd� d�S )zatarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent.c S s | j jjp | j jjp | j jjS r' )r. rN Zsupports_empty_insertZsupports_default_valuesZsupports_default_metavaluer0 r r r r* s �z1SuiteRequirements.empty_inserts.<locals>.<lambda>zempty inserts not supportedr+ r r r r � empty_insertsy s �z SuiteRequirements.empty_insertsc C s | j S )zvtarget platform supports INSERT with no values, i.e. INSERT DEFAULT VALUES or equivalent, within executemany())rV r r r r �empty_inserts_executemany� s z+SuiteRequirements.empty_inserts_executemanyc C s t �� S )z.target platform supports INSERT from a SELECT.r r r r r �insert_from_select� s z$SuiteRequirements.insert_from_selectc C s t �dd� d�S )z.target platform supports DELETE ... RETURNING.c S s | j jjS r' )r. rN �delete_returningr0 r r r r* � rO z4SuiteRequirements.delete_returning.<locals>.<lambda>z4%(database)s %(does_support)s 'DELETE ... RETURNING'r+ r r r r rY � s �z"SuiteRequirements.delete_returningc C s t �dd� d�S )z.target platform supports INSERT ... RETURNING.c S s | j jjS r' )r. rN �insert_returningr0 r r r r* � rO z4SuiteRequirements.insert_returning.<locals>.<lambda>z4%(database)s %(does_support)s 'INSERT ... RETURNING'r+ r r r r rZ � s �z"SuiteRequirements.insert_returningc C s t �dd� d�S )z.target platform supports UPDATE ... RETURNING.c S s | j jjS r' )r. rN �update_returningr0 r r r r* � rO z4SuiteRequirements.update_returning.<locals>.<lambda>z4%(database)s %(does_support)s 'UPDATE ... RETURNING'r+ r r r r r[ � s �z"SuiteRequirements.update_returningc C s t �dd� d�S )z�target 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. c S s | j jjS r' )r. rN � insert_executemany_returningr0 r r r r* � rO z@SuiteRequirements.insert_executemany_returning.<locals>.<lambda>zR%(database)s %(does_support)s 'RETURNING of multiple rows with INSERT executemany'r+ r r r r r\ � s �z.SuiteRequirements.insert_executemany_returningc C s t �dd� d�S )Nc S s | j jjo | j jjo | j jjS r' )r. rN �supports_multivalues_insertrZ Zuse_insertmanyvaluesr0 r r r r* � s �z4SuiteRequirements.insertmanyvalues.<locals>.<lambda>z=%(database)s %(does_support)s 'insertmanyvalues functionalityr+ r r r r �insertmanyvalues� s �z"SuiteRequirements.insertmanyvaluesc C s t �� S )zZTarget platform supports the syntax "(x, y) IN ((x1, y1), (x2, y2), ...)" r r r r r �tuple_in� s zSuiteRequirements.tuple_inc C s | j S )z%Target platform tuple IN w/ empty set)r_ r r r r �tuple_in_w_empty� s z"SuiteRequirements.tuple_in_w_emptyc C s t �� S )zwtarget platform supports a SELECT statement that has the same name repeated more than once in the columns list.r r r r r �%duplicate_names_in_cursor_description� s z7SuiteRequirements.duplicate_names_in_cursor_descriptionc C s t �dd� d�S )z[Target database must have 'denormalized', i.e. UPPERCASE as case insensitive names.c S s | j jj S r' )r. rN Zrequires_name_normalizer0 r r r r* � rO z6SuiteRequirements.denormalized_names.<locals>.<lambda>z,Backend does not require denormalized names.rP r r r r �denormalized_names� s �z$SuiteRequirements.denormalized_namesc C s t �dd� d�S )zTtarget database must support multiple VALUES clauses in an INSERT statement.c S s | j jj S r' )r. rN r] r0 r r r r* � rO z7SuiteRequirements.multivalues_inserts.<locals>.<lambda>z*Backend does not support multirow inserts.rP r r r r �multivalues_inserts� s �z%SuiteRequirements.multivalues_insertsc C s t �� S )zvtarget dialect implements the executioncontext.get_lastrowid() method without reliance on RETURNING. r r r r r �implements_get_lastrowid� s z*SuiteRequirements.implements_get_lastrowidc C s t �� S )zLdialect includes the required pep-249 attribute ``cursor.arraysize``r r r r r � arraysize� s zSuiteRequirements.arraysizec C s t �� S )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. r r r r r �emulated_lastrowid� s z$SuiteRequirements.emulated_lastrowidc C s t �� S )z�target dialect retrieves cursor.lastrowid or an equivalent after an insert() construct executes, even if the table has a Sequence on it. r r r r r �&emulated_lastrowid_even_with_sequences s z8SuiteRequirements.emulated_lastrowid_even_with_sequencesc C s t �� S )z]target platform includes a 'lastrowid' accessor on the DBAPI cursor object. r r r r r �dbapi_lastrowid s z!SuiteRequirements.dbapi_lastrowidc C s t �� S )z#Target database must support VIEWs.r r r r r �views s zSuiteRequirements.viewsc C s t dd� �S )zXTarget database must support external schemas, and have one named 'test_schema'.c S s | j jjS r' )r. rN Zsupports_schemasr0 r r r r* # rO z+SuiteRequirements.schemas.<locals>.<lambda>r r r r r �schemas s zSuiteRequirements.schemasc C s t �� S )zJtarget system must support reflection of inter-schema foreign keysr r r r r �cross_schema_fk_reflection% s z,SuiteRequirements.cross_schema_fk_reflectionc C s t �� S )a Target supports reflection of FOREIGN KEY constraints and will return the name of the constraint that was used in the "CONSTRAINT <name> FOREIGN KEY" DDL. MySQL prior to version 8 and MariaDB prior to version 10.5 don't support this. r r r r r �&foreign_key_constraint_name_reflection+ s z8SuiteRequirements.foreign_key_constraint_name_reflectionc C s t �� S )z�target system has a strong concept of 'default' schema that can be referred to implicitly. basically, PostgreSQL. r r r r r �implicit_default_schema7 s z)SuiteRequirements.implicit_default_schemac C s t �� S )z`target dialect implements provisioning module including set_default_schema_on_connectionr r r r r �default_schema_name_switchA s z,SuiteRequirements.default_schema_name_switchc C s t �dd� gd�S )z0Target dialect must support server side cursors.c S s | j jjS r' )r. rN Z supports_server_side_cursorsr0 r r r r* M rO z7SuiteRequirements.server_side_cursors.<locals>.<lambda>z no server side cursors supportr+ r r r r �server_side_cursorsH s �z%SuiteRequirements.server_side_cursorsc C s t �dd� gd�S )z'Target database must support SEQUENCEs.c S s | j jjS r' )r. rN �supports_sequencesr0 r r r r* V rO z-SuiteRequirements.sequences.<locals>.<lambda>zno sequence supportr+ r r r r � sequencesQ s �zSuiteRequirements.sequencesc C s t �| j�S )zJthe opposite of "sequences", DB does not support sequences at all.)r Z NotPredicaterq r r r r � no_sequencesZ s z SuiteRequirements.no_sequencesc C s t �dd� gd�S )zgTarget database supports sequences, but also optionally as a means of generating new PK values.c S s | j jjo| j jjS r' )r. rN rp �sequences_optionalr0 r r r r* h s z6SuiteRequirements.sequences_optional.<locals>.<lambda>z.no sequence support, or sequences not optionalr+ r r r r rs a s ��z$SuiteRequirements.sequences_optionalc C s t �dd� g�S )a target 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. c S s | j jjS r' �r. rN Zpostfetch_lastrowidr0 r r r r* x rO z6SuiteRequirements.supports_lastrowid.<locals>.<lambda>r+ r r r r �supports_lastrowidn s �z$SuiteRequirements.supports_lastrowidc C s t �dd� g�S )z"the opposite of supports_lastrowidc S s | j jj S r' rt r0 r r r r* rO z8SuiteRequirements.no_lastrowid_support.<locals>.<lambda>r+ r r r r �no_lastrowid_support{ s �z&SuiteRequirements.no_lastrowid_supportc C s t �� S r' r r r r r �reflects_pk_names� s z#SuiteRequirements.reflects_pk_namesc C s t �� S )z8target database has general support for table reflectionr r r r r �table_reflection� s z"SuiteRequirements.table_reflectionc C s t �� S )z�target database supports creation and reflection of tables with no columns, or at least tables that seem to have no columns.r r r r r �reflect_tables_no_columns� s z+SuiteRequirements.reflect_tables_no_columnsc C s t �� S )z:Indicates if the database support table comment reflectionr r r r r �comment_reflection� s z$SuiteRequirements.comment_reflectionc C s t �� S )z{Indicates if the database support table comment reflection in the full unicode range, including emoji etc. r r r r r � comment_reflection_full_unicode� s z1SuiteRequirements.comment_reflection_full_unicodec C s t �� S )zVindicates if the database support comments on constraints and their reflectionr r r r r � constraint_comment_reflection� s z/SuiteRequirements.constraint_comment_reflectionc C s | j S )z�target 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. �ri r r r r �view_column_reflection� s z(SuiteRequirements.view_column_reflectionc C s | j S )zStarget database must support inspection of the full CREATE VIEW definition.r} r r r r �view_reflection� s z!SuiteRequirements.view_reflectionc C s | j S r' )rj r r r r �schema_reflection� s z#SuiteRequirements.schema_reflectionc C s t �� S )zatarget database supports schema create and dropped with 'CREATE SCHEMA' and 'DROP SCHEMA'r r r r r �schema_create_delete� s z&SuiteRequirements.schema_create_deletec C s t �� S r' r r r r r �!primary_key_constraint_reflection� s z3SuiteRequirements.primary_key_constraint_reflectionc C s t �� S r' r r r r r �!foreign_key_constraint_reflection� s z3SuiteRequirements.foreign_key_constraint_reflectionc C s t �� S r' r r r r r �1foreign_key_constraint_option_reflection_ondelete� s zCSuiteRequirements.foreign_key_constraint_option_reflection_ondeletec C s t �� S r' r r r r r �1fk_constraint_option_reflection_ondelete_restrict� s zCSuiteRequirements.fk_constraint_option_reflection_ondelete_restrictc C s t �� S r' r r r r r �1fk_constraint_option_reflection_ondelete_noaction� s zCSuiteRequirements.fk_constraint_option_reflection_ondelete_noactionc C s t �� S r' r r r r r �1foreign_key_constraint_option_reflection_onupdate� s zCSuiteRequirements.foreign_key_constraint_option_reflection_onupdatec C s t �� S r' r r r r r �1fk_constraint_option_reflection_onupdate_restrict� s zCSuiteRequirements.fk_constraint_option_reflection_onupdate_restrictc C s t �� S r' r r r r r �temp_table_reflection� s z'SuiteRequirements.temp_table_reflectionc C s | j S r' )r� r r r r �temp_table_reflect_indexes� s z,SuiteRequirements.temp_table_reflect_indexesc C s t �� S )z8target dialect supports listing of temporary table namesr r r r r �temp_table_names� s z"SuiteRequirements.temp_table_namesc C s t �� S )z9target dialect supports checking a single temp table namer r r r r �has_temp_table� s z SuiteRequirements.has_temp_tablec C s t �� S )z)target database supports temporary tablesr r r r r �temporary_tables� s z"SuiteRequirements.temporary_tablesc C s t �� S )z(target database supports temporary viewsr r r r r �temporary_views� s z!SuiteRequirements.temporary_viewsc C s t �� S r' r r r r r �index_reflection� s z"SuiteRequirements.index_reflectionc C s t �� S r' r r r r r � index_reflects_included_columns� s z1SuiteRequirements.index_reflects_included_columnsc C s t �� S )z?target database supports CREATE INDEX with per-column ASC/DESC.r r r r r �indexes_with_ascdesc� s z&SuiteRequirements.indexes_with_ascdescc C s t �� S )zKtarget database supports reflecting INDEX with per-column ASC/DESC.r r r r r � reflect_indexes_with_ascdesc s z.SuiteRequirements.reflect_indexes_with_ascdescc C s t �� S )zztarget database supports reflecting INDEX with per-column ASC/DESC but reflects them as expressions (like oracle).r r r r r �*reflect_indexes_with_ascdesc_as_expression s z<SuiteRequirements.reflect_indexes_with_ascdesc_as_expressionc C s t �� S )z>target database supports CREATE INDEX against SQL expressions.r r r r r �indexes_with_expressions s z*SuiteRequirements.indexes_with_expressionsc C s t �� S )zLtarget database supports reflection of indexes with SQL expressions.r r r r r � reflect_indexes_with_expressions s z2SuiteRequirements.reflect_indexes_with_expressionsc C s t �� S )z8target dialect supports reflection of unique constraintsr r r r r � unique_constraint_reflection s z.SuiteRequirements.unique_constraint_reflectionc C s t �� S )z7target dialect supports reflection of check constraintsr r r r r �check_constraint_reflection s z-SuiteRequirements.check_constraint_reflectionc C s t �� S )z�target dialect raises IntegrityError when reporting an INSERT with a primary key violation. (hint: it should) r r r r r �$duplicate_key_raises_integrity_error$ s z6SuiteRequirements.duplicate_key_raises_integrity_errorc C s t �� S )z3Target database must support VARCHAR with no lengthr r r r r �unbounded_varchar, s z#SuiteRequirements.unbounded_varcharc C s t �� S )z�Target 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. r r r r r � unicode_data_no_special_types2 s z/SuiteRequirements.unicode_data_no_special_typesc C s t �� S )z�Target database/dialect must support Python unicode objects with non-ASCII characters represented, delivered as bound parameters as well as in result rows. r r r r r � unicode_data; s z SuiteRequirements.unicode_datac C s t �� S )zRTarget driver must support some degree of non-ascii symbol names. r r r r r � unicode_ddlD s z SuiteRequirements.unicode_ddlc C s t �� S )z?Target driver can create tables with a name like 'some " table'r r r r r �symbol_names_w_double_quoteK s z-SuiteRequirements.symbol_names_w_double_quotec C s t �� S )z�target dialect supports rendering of a datetime.timedelta as a literal string, e.g. via the TypeEngine.literal_processor() method. r r r r r �datetime_intervalP s z#SuiteRequirements.datetime_intervalc C s t �� S )z�target dialect supports rendering of a date, time, or datetime as a literal string, e.g. via the TypeEngine.literal_processor() method. r r r r r �datetime_literalsX s z#SuiteRequirements.datetime_literalsc C s t �� S )zUtarget dialect supports representation of Python datetime.datetime() objects.r r r r r �datetimea s zSuiteRequirements.datetimec C s t �� S )zvtarget dialect supports representation of Python datetime.datetime() with tzinfo with DateTime(timezone=True).r r r r r �datetime_timezoneh s z#SuiteRequirements.datetime_timezonec C s t �� S )zntarget dialect supports representation of Python datetime.time() with tzinfo with Time(timezone=True).r r r r r � time_timezoneo s z SuiteRequirements.time_timezonec C s t �� S )z�target 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. r r r r r �date_implicit_boundv s z%SuiteRequirements.date_implicit_boundc C s t �� S )z�target 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. r r r r r �time_implicit_bound s z%SuiteRequirements.time_implicit_boundc C s t �� S )z�target 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. r r r r r �datetime_implicit_bound� s z)SuiteRequirements.datetime_implicit_boundc C s t �� S )zftarget dialect supports representation of Python datetime.datetime() with microsecond objects.r r r r r �datetime_microseconds� s z'SuiteRequirements.datetime_microsecondsc C s t �� S )z�target dialect supports representation of Python datetime.datetime() with microsecond objects but only if TIMESTAMP is used.r r r r r �timestamp_microseconds� s z(SuiteRequirements.timestamp_microsecondsc C s | j S )a target 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. )r� r r r r �%timestamp_microseconds_implicit_bound� s z7SuiteRequirements.timestamp_microseconds_implicit_boundc C s t �� S �zutarget dialect supports representation of Python datetime.datetime() objects with historic (pre 1970) values.r r r r r �datetime_historic� s z#SuiteRequirements.datetime_historicc C s t �� S )zQtarget dialect supports representation of Python datetime.date() objects.r r r r r �date� s zSuiteRequirements.datec C s t �� S )zPtarget dialect accepts a datetime object as the target of a date column.r r r r r �date_coerces_from_datetime� s z,SuiteRequirements.date_coerces_from_datetimec C s t �� S r� r r r r r � date_historic� s z SuiteRequirements.date_historicc C s t �� S )zQtarget dialect supports representation of Python datetime.time() objects.r r r r r �time� s zSuiteRequirements.timec C s t �� S )zbtarget dialect supports representation of Python datetime.time() with microsecond objects.r r r r r �time_microseconds� s z#SuiteRequirements.time_microsecondsc C s t �� S )zttarget database/driver can allow BLOB/BINARY fields to be compared against a bound parameter value. r r r r r �binary_comparisons� s z$SuiteRequirements.binary_comparisonsc C s t �� S )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. r r r r r �binary_literals� s z!SuiteRequirements.binary_literalsc C s t �� S )z:target dialect supports 'AUTOCOMMIT' as an isolation_levelr r r r r � autocommit� s z SuiteRequirements.autocommitc C s t �� S )z�target dialect supports general isolation level settings. Note that this requirement, when enabled, also requires that the get_isolation_levels() method be implemented. r r r r r �isolation_level� s z!SuiteRequirements.isolation_levelc C sj |j �� �V}z|j�|jj�}W n tk r@ Y W 5 Q R � dS X |jj|d�W 5 Q R � S W 5 Q R X dS )a� Return a structure of supported isolation levels for the current testing dialect. The structure indicates to the testing suite what the expected "default" isolation should be, as well as the other values that are accepted. The dictionary has two keys, "default" and "supported". The "supported" key refers to a list of all supported levels and it should include AUTOCOMMIT if the dialect supports it. If the :meth:`.DefaultRequirements.isolation_level` requirement is not open, then this method has no return value. E.g.:: >>> testing.requirements.get_isolation_levels() { "default": "READ_COMMITTED", "supported": [ "SERIALIZABLE", "READ UNCOMMITTED", "READ COMMITTED", "REPEATABLE READ", "AUTOCOMMIT" ] } N)�default� supported)r. �connectrN �get_isolation_level_values� connection�dbapi_connection�NotImplementedErrorZdefault_isolation_level)r r1 �connr� r r r �get_isolation_levels� s ��z&SuiteRequirements.get_isolation_levelsc C s dd� }t �|�S )z�target dialect supports the :meth:`_engine.Dialect.get_isolation_level_values` method added in SQLAlchemy 2.0. c S s^ | j �� �J}z|j�|jj� W n tk r@ Y W 5 Q R � dS X W 5 Q R � dS W 5 Q R X d S �NFT)r. r� rN r� r� r� r� )r1 r� r r r r2 ( s �z8SuiteRequirements.get_isolation_level_values.<locals>.gor+ r3 r r r r� s z,SuiteRequirements.get_isolation_level_valuesc C s dd� }t �|�S )zctest that the dialect allows the 'isolation_level' argument to be handled by DefaultDialectc S s4 zt | jjdd�}W n Y dS X |jjdkS d S )NzREAD COMMITTED)r� F)r r. �urlrN Z_on_connect_isolation_level)r1 �er r r r2 : s � �zASuiteRequirements.dialect_level_isolation_level_param.<locals>.gor+ r3 r r r �#dialect_level_isolation_level_param5 s z5SuiteRequirements.dialect_level_isolation_level_paramc C s t �� S )z.target platform implements a native JSON type.r r r r r � json_typeH s zSuiteRequirements.json_typec C s | j S )zNtarget platform supports numeric array indexes within a JSON structure)r� r r r r �json_array_indexesN s z$SuiteRequirements.json_array_indexesc C s t �� S r' r r r r r �(json_index_supplementary_unicode_elementU s z:SuiteRequirements.json_index_supplementary_unicode_elementc C s t �� S )z�Backend 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 r r r r �!legacy_unconditional_json_extractY s z3SuiteRequirements.legacy_unconditional_json_extractc C s t �� S )zRtarget backend has general support for moderately high-precision numerics.r r r r r �precision_numerics_generalc s z,SuiteRequirements.precision_numerics_generalc C s t �� S )zbtarget backend supports Decimal() objects using E notation to represent very small values.r r r r r �"precision_numerics_enotation_smalli s z4SuiteRequirements.precision_numerics_enotation_smallc C s t �� S )zbtarget backend supports Decimal() objects using E notation to represent very large values.r r r r r �"precision_numerics_enotation_largeo s z4SuiteRequirements.precision_numerics_enotation_largec C s t �� S )z�target backend supports values with many digits on both sides, such as 319438950232418390.273596, 87673.594069654243 r r r r r �*precision_numerics_many_significant_digitsu s z<SuiteRequirements.precision_numerics_many_significant_digitsc C s | j S )z}same as precision_numerics_many_significant_digits but within the context of a CAST statement (hello MySQL) )r� r r r r �/cast_precision_numerics_many_significant_digits} s zASuiteRequirements.cast_precision_numerics_many_significant_digitsc C s t �� S )a+ target 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` r r r r r �implicit_decimal_binds� s z(SuiteRequirements.implicit_decimal_bindsc C s t �� S )aF target 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. r r r r r �#numeric_received_as_decimal_untyped� s z5SuiteRequirements.numeric_received_as_decimal_untypedc C s t �� S )zhtarget database can select an aggregate from a subquery that's also using an aggregate r r r r r �nested_aggregates� s z#SuiteRequirements.nested_aggregatesc C s t �� S )zbtarget database must support ON DELETE CASCADE on a self-referential foreign key r r r r r �recursive_fk_cascade� s z&SuiteRequirements.recursive_fk_cascadec C s t �� S )z�A 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 r r r r �-precision_numerics_retains_significant_digits� s z?SuiteRequirements.precision_numerics_retains_significant_digitsc C s t �� S )z@The Float type can persist and load float('inf'), float('-inf').r r r r r �infinity_floats� s z!SuiteRequirements.infinity_floatsc C s t �� S r' r r r r r �-float_or_double_precision_behaves_generically� s z?SuiteRequirements.float_or_double_precision_behaves_genericallyc C s t �� S )z�target backend will return native floating point numbers with at least seven decimal places when using the generic Float type. r r r r r � precision_generic_float_type� s z.SuiteRequirements.precision_generic_float_typec C s t �� S )z�target 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 r r r r r �literal_float_coercion� s z(SuiteRequirements.literal_float_coercionc C s t �� S )z�target 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). r r r r r �floats_to_four_decimals� s z)SuiteRequirements.floats_to_four_decimalsc C s t �� S )z�target backend doesn't crash when you try to select a NUMERIC value that has a value of NULL. Added to support Pyodbc bug #351. r r r r r �fetch_null_from_numeric� s z)SuiteRequirements.fetch_null_from_numericc C s t �� S )z*target backend uses Numeric for Float/Dualr r r r r �float_is_numeric� s z"SuiteRequirements.float_is_numericc C s t �� S )zUTarget database must support an unbounded Text() " "type such as TEXT or CLOBr r r r r � text_type� s zSuiteRequirements.text_typec C s t �� S )zTtarget database can persist/return an empty string with a varchar. r r r r r �empty_strings_varchar s z'SuiteRequirements.empty_strings_varcharc C s t �� S )zRtarget database can persist/return an empty string with an unbounded text.r r r r r �empty_strings_text s z$SuiteRequirements.empty_strings_textc C s t �� S )zUtarget database supports use of an unbounded textual field in a WHERE clause.r r r r r �"expressions_against_unbounded_text s z4SuiteRequirements.expressions_against_unbounded_textc C s t �� S )z;target driver must support the literal statement 'select 1'r r r r r � selectone s zSuiteRequirements.selectonec C s t �� S )z(Target database must support savepoints.r r r r r � savepoints s z SuiteRequirements.savepointsc C s t �� S )z4Target database must support two-phase transactions.r r r r r �two_phase_transactions" s z(SuiteRequirements.two_phase_transactionsc C s t �� S )z'Target must support UPDATE..FROM syntaxr r r r r � update_from( s z SuiteRequirements.update_fromc C s t �� S )z=Target must support DELETE FROM..FROM or DELETE..USING syntaxr r r r r � delete_from- s z SuiteRequirements.delete_fromc C s t �� S )a� Target 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 ) r r r r r � update_where_target_in_subquery2 s z1SuiteRequirements.update_where_target_in_subqueryc C s t �� S )zOtarget database must use a plain percent '%' as the 'modulus' operator.r r r r r � mod_operator_as_percent_signB s z.SuiteRequirements.mod_operator_as_percent_signc C s t �� S )a target 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 r r r r �percent_schema_namesH s z&SuiteRequirements.percent_schema_namesc C s t �� S )z�target database supports ordering by a column from a SELECT inside of a UNION E.g. (SELECT id, ...) UNION (SELECT id, ...) ORDER BY id r r r r r �order_by_col_from_unionT s z)SuiteRequirements.order_by_col_from_unionc C s t �� S )a target 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 r r r r � order_by_label_with_expression^ s z0SuiteRequirements.order_by_label_with_expressionc s � fdd�}t �|�S )Nc s, z� � | � W dS tk r& Y dS X d S r� )�get_order_by_collationr� r0 r r r �checko s z3SuiteRequirements.order_by_collation.<locals>.checkrP �r r� r r r �order_by_collationm s z$SuiteRequirements.order_by_collationc C s t � �d S r' )r� �r r1 r r r r� x s z(SuiteRequirements.get_order_by_collationc C s t �� S )zUTarget driver must support non-ASCII characters being passed at all. r r r r r �unicode_connections{ s z%SuiteRequirements.unicode_connectionsc C s t �� S )z�Target driver must raise a DBAPI-level exception, such as InterfaceError, when the underlying connection has been closed and the execute() method is called. r r r r r �graceful_disconnects� s z&SuiteRequirements.graceful_disconnectsc C s t �� S )zU Target must support simultaneous, independent database connections. r r r r r �independent_connections� s z)SuiteRequirements.independent_connectionsc C s t �� S )z� Target must support simultaneous, independent database connections that will be used in a readonly fashion. r r r r r � independent_readonly_connections� s z2SuiteRequirements.independent_readonly_connectionsc C s t �� S )z9Catchall for a large variety of MySQL on Windows failuresr r r r r �skip_mysql_on_windows� s z'SuiteRequirements.skip_mysql_on_windowsc C s t �dd� �S )a Test 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 S s | j jS r' )�optionsZlow_connectionsr0 r r r r* � rO z2SuiteRequirements.ad_hoc_engines.<locals>.<lambda>rP r r r r �ad_hoc_engines� s �z SuiteRequirements.ad_hoc_enginesc C s t �| �� �S r' )r rQ �_running_on_windowsr r r r � no_windows� s z SuiteRequirements.no_windowsc C s t jdd� dd�S )Nc S s t �� dkS )N�Windows)�platform�systemr r r r r* � rO z7SuiteRequirements._running_on_windows.<locals>.<lambda>zrunning on Windows)� description)r ZLambdaPredicater r r r r� � s �z%SuiteRequirements._running_on_windowsc C s ddl m} |jjS �Nr r0 )� r1 � add_to_marker�timing_intensiver� r r r r� � s z"SuiteRequirements.timing_intensivec C s ddl m} |jjS r� )r� r1 r� �memory_intensiver� r r r r� � s z"SuiteRequirements.memory_intensivec C s t �dd� d�S )z}Mark tests that use threading and mock at the same time - stability issues have been observed with coverage c S s | j jS r' �r� Z has_coverager0 r r r r* � rO z7SuiteRequirements.threading_with_mock.<locals>.<lambda>z Stability issues with coveragerP r r r r �threading_with_mock� s �z%SuiteRequirements.threading_with_mockc C s dd� }t �|�S )Nc S s, z t d� W n tk r" Y dS X dS d S �Nzsqlalchemy-stubs.ext.mypyFT�� __import__� ImportErrorr0 r r r r� � s z2SuiteRequirements.sqlalchemy2_stubs.<locals>.checkr+ r� r r r �sqlalchemy2_stubs� s z#SuiteRequirements.sqlalchemy2_stubsc C s dd� }t �|�S )Nc S s, z t d� W n tk r" Y dS X dS d S r� r� r0 r r r r� � s z5SuiteRequirements.no_sqlalchemy2_stubs.<locals>.checkrP r� r r r �no_sqlalchemy2_stubs� s z&SuiteRequirements.no_sqlalchemy2_stubsc C s t �dd� d�S )Nc S s t jS r' )r Zpy38r r r r r* � rO z,SuiteRequirements.python38.<locals>.<lambda>z Python 3.8 or above requiredr+ r r r r �python38� s �zSuiteRequirements.python38c C s t �dd� d�S )Nc S s t jS r' )r Zpy39r r r r r* � rO z,SuiteRequirements.python39.<locals>.<lambda>z Python 3.9 or above requiredr+ r r r r �python39� s �zSuiteRequirements.python39c C s t �dd� d�S )Nc S s t jS r' )r Zpy310r r r r r* � rO z-SuiteRequirements.python310.<locals>.<lambda>z Python 3.10 or above requiredr+ r r r r � python310� s �zSuiteRequirements.python310c C s t �dd� d�S )Nc S s t jS r' )r Zpy311r r r r r* � rO z-SuiteRequirements.python311.<locals>.<lambda>z Python 3.11 or above requiredr+ r r r r � python311� s �zSuiteRequirements.python311c C s t �dd� d�S )Nc S s t jS r' )r Zpy312r r r r r* rO z-SuiteRequirements.python312.<locals>.<lambda>z Python 3.12 or above requiredr+ r r r r � python312� s �zSuiteRequirements.python312c C s t �dd� d�S )Nc S s t jS r' )r �cpythonr r r r r* rO z+SuiteRequirements.cpython.<locals>.<lambda>zcPython interpreter neededr+ r r r r r s �zSuiteRequirements.cpythonc C s t �dd� d�S )Nc S s t jS r' )r �is64bitr r r r r* rO z+SuiteRequirements.is64bit.<locals>.<lambda>z64bit requiredr+ r r r r r s zSuiteRequirements.is64bitc C s dd� }t �|d�S )Nc S s, z t d� W n tk r" Y dS X dS d S )N�patchFTr� r r r r � check_lib s z2SuiteRequirements.patch_library.<locals>.check_libzpatch library neededr+ )r r r r r � patch_library s z SuiteRequirements.patch_libraryc C s | j S )z�target platform must remove all cycles unconditionally when gc.collect() is called, as well as clean out unreferenced subclasses. )r r r r r �predictable_gc s z SuiteRequirements.predictable_gcc C s t �dd� d�S )z�Test 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 S s | j jS r' r� r0 r r r r* * rO z/SuiteRequirements.no_coverage.<locals>.<lambda>z(Issues observed when coverage is enabledrP r r r r � no_coverage! s �z SuiteRequirements.no_coveragec C s dS �NFr r� r r r �_has_mysql_on_windows. s z'SuiteRequirements._has_mysql_on_windowsc C s dS r r r� r r r � _has_mysql_fully_case_sensitive1 s z1SuiteRequirements._has_mysql_fully_case_sensitivec s t �� fdd��S )Nc s � � � S r' )� _has_sqliter r r r r* 6 rO z*SuiteRequirements.sqlite.<locals>.<lambda>rP r r r r �sqlite4 s zSuiteRequirements.sqlitec C s t �dd� d�S )Nc S s t �� S r' )r Zhas_compiled_extr r r r r* ; rO z/SuiteRequirements.cextensions.<locals>.<lambda>z Cython extensions not installedrP r r r r � cextensions8 s �z SuiteRequirements.cextensionsc C s6 ddl m} z|d� W dS tk r0 Y dS X d S )Nr r z sqlite://TF)Z sqlalchemyr r )r r r r r r ? s z SuiteRequirements._has_sqlitec C s t �� S )z@dialect makes use of await_() to invoke operations on the DBAPI.r r r r r � async_dialectH s z SuiteRequirements.async_dialectc C s | j S r' )�greenletr r r r r N s zSuiteRequirements.asyncioc C s dd� }t �|�S )Nc S s, z dd l }W n tk r" Y dS X dS d S )Nr TF)r r �r1 r r r r r2 T s z)SuiteRequirements.no_greenlet.<locals>.gor+ r3 r r r � no_greenletR s z SuiteRequirements.no_greenletc C s dd� }t �|�S )Nc S s6 t js dS z dd l}W n tk r, Y dS X dS d S )NFr T)� _test_asyncioZENABLE_ASYNCIOr r r r r r r2 ` s z&SuiteRequirements.greenlet.<locals>.gor+ r3 r r r r ^ s zSuiteRequirements.greenletc C s t �� S )zSupports computed columnsr r r r r �computed_columnsm s z"SuiteRequirements.computed_columnsc C s t �� S )z/Supports computed columns with `persisted=True`r r r r r �computed_columns_storedr s z)SuiteRequirements.computed_columns_storedc C s t �� S )z0Supports computed columns with `persisted=False`r r r r r �computed_columns_virtualw s z*SuiteRequirements.computed_columns_virtualc C s t �� S )zSIf the default persistence is virtual or stored when `persisted` is omittedr r r r r �"computed_columns_default_persisted| s z4SuiteRequirements.computed_columns_default_persistedc C s t �� S )zTIf persistence information is returned by the reflection of computed columnsr r r r r �"computed_columns_reflect_persisted� s z4SuiteRequirements.computed_columns_reflect_persistedc C s t �� S )z1If a backend supports the DISTINCT ON in a selectr r r r r �supports_distinct_on� s z&SuiteRequirements.supports_distinct_onc C s t �dd� d�S )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` c S s | j jj S r' )r. rN �supports_is_distinct_fromr0 r r r r* � rO z=SuiteRequirements.supports_is_distinct_from.<locals>.<lambda>z4driver doesn't support an IS DISTINCT FROM constructrP r r r r r � s �z+SuiteRequirements.supports_is_distinct_fromc C s t �� S )zKIf a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITYr r r r r �identity_columns� s z"SuiteRequirements.identity_columnsc C s t �� S )z�If a backend supports GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY with a standard syntax. This is mainly to exclude MSSql. r r r r r �identity_columns_standard� s z+SuiteRequirements.identity_columns_standardc C s t �� S )z+backend supports the regexp_match operator.r r r r r � regexp_match� s z SuiteRequirements.regexp_matchc C s t �� S )z-backend supports the regexp_replace operator.r r r r r �regexp_replace� s z SuiteRequirements.regexp_replacec C s t �� S )z(backend supports the fetch first clause.r r r r r � fetch_first� s z SuiteRequirements.fetch_firstc C s t �� S )z5backend supports the fetch first clause with percent.r r r r r � fetch_percent� s z SuiteRequirements.fetch_percentc C s t �� S )z2backend supports the fetch first clause with ties.r r r r r � fetch_ties� s z SuiteRequirements.fetch_tiesc C s t �� S )z1backend supports the fetch first without order byr r r r r �fetch_no_order_by� s z#SuiteRequirements.fetch_no_order_byc C s t �� S )zwbackend supports the offset when using fetch first with percent or ties. basically this is "not mssql" r r r r r �fetch_offset_with_options� s z+SuiteRequirements.fetch_offset_with_optionsc C s t �� S )z�backend supports fetch / offset with expression in them, like SELECT * FROM some_table OFFSET 1 + 1 ROWS FETCH FIRST 1 + 1 ROWS ONLY r r r r r �fetch_expression� s z"SuiteRequirements.fetch_expressionc C s t �� S )zIf autoincrement=True on a column does not require an explicit sequence. This should be false only for oracle. r r r r r � autoincrement_without_sequence� s z0SuiteRequirements.autoincrement_without_sequencec C s t �� S )z=If X[Y] can be implemented with ``__class_getitem__``. py3.7+r r r r r �generic_classes� s z!SuiteRequirements.generic_classesc C s t �� S )z@indicates if the json_deserializer function is called with bytesr r r r r �json_deserializer_binary� s z*SuiteRequirements.json_deserializer_binaryc C s t �� S )z6Target database must support reflecting table_options.r r r r r �reflect_table_options� s z'SuiteRequirements.reflect_table_optionsc C s t �� S )z0Target database must support MATERIALIZED VIEWs.r r r r r �materialized_views� s z$SuiteRequirements.materialized_viewsc C s t �� S )z/Target database reflect MATERIALIZED VIEWs pks.r r r r r � materialized_views_reflect_pk� s z/SuiteRequirements.materialized_views_reflect_pkc C s t �� S )z#Target database supports bitwise orr r r r r �supports_bitwise_or� s z%SuiteRequirements.supports_bitwise_orc C s t �� S )z$Target database supports bitwise andr r r r r �supports_bitwise_and� s z&SuiteRequirements.supports_bitwise_andc C s t �� S )z$Target database supports bitwise notr r r r r �supports_bitwise_not s z&SuiteRequirements.supports_bitwise_notc C s t �� S )z$Target database supports bitwise xorr r r r r �supports_bitwise_xor s z&SuiteRequirements.supports_bitwise_xorc C s t �� S )z4Target database supports bitwise left or right shiftr r r r r �supports_bitwise_shift s z(SuiteRequirements.supports_bitwise_shiftN)�r r r �propertyr r r r r r r r! r" r# r$ r% r& r( r, r4 r5 r6 r7 r8 r9 r: r; r< r= r> r? r@ rA rB rC rD rE rF rG rH rI rJ rK rL rM rR rT rU rV rW rX rY rZ r[ r\ r^ r_ r` ra rb rc rd re rf rg rh ri rj rk rl rm rn ro rq rr rs ru rv rw rx ry rz r{ r| r~ r r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r� r r r r r r r r r r r r r r r r r r r r r r r r r r r r r! r" r# r$ r% r& r' r( r) r* r+ r, r- r. r/ r0 r1 r2 r3 r4 r5 r r r r r $ s� & r )�__doc__� __future__r r� r� r r r r r r r/ r r r r r r r �<module> s