wed< Z?ed= Z@ed> ZAed? ZBed@ ZCedA ZDedB ZEedC ZFedD ZGedE ZHedF ZIedG ZJedH ZKedI ZLedJ ZMedK ZNedL ZOedM ZPedN ZQedO ZRedP ZSedQ ZTedR ZUedS ZVedT ZWedU ZXedV ZYedW ZZedX Z[edY Z\edZ Z]ed[ Z^ed\ Z_d] Z`ed^ Zaed_ Zbed` Zceda Zdedb Zeedc Zfedd Zgede Zhedf Ziedg Zjedh Zkedi Zledj Zmedk Znedl Zoedm Zpedn Zqedo Zredp Zsedq Ztedr Zueds Zvedt Zwedu Zxedv Zyedw Zzedx Z{edy Z|edz Z}d{ Z~ed| Zed} Zed~ Zed Zed Zed Zed Zed Zed Zed Zed Zed Zed Zed Zed Zed Zed Zd Zd Zed Zed Zd Zd Zed Zed Zed Zed Zed Zed ZdS )SuiteRequirementsc ( t j S )z/target platform can emit basic CreateTable DDL.r openselfs r create_tablez SuiteRequirements.create_table r
c ( t j S )z-target platform can emit basic DropTable DDL.r r s r
drop_tablez SuiteRequirements.drop_table# r r
c ( t j S )z*Target database must support foreign keys.r r s r foreign_keysz SuiteRequirements.foreign_keys) r r
c ( t j S )zQtarget database must support ON UPDATE..CASCADE behavior in
foreign keys.r r s r on_update_cascadez#SuiteRequirements.on_update_cascade/
r
c ( t j S )zWtarget database must *not* support ON UPDATE..CASCADE behavior in
foreign keys.r closedr s r non_updating_cascadez&SuiteRequirements.non_updating_cascade6 """r
c ( t j S Nr r s r deferrable_fksz SuiteRequirements.deferrable_fks< """r
c 2 t j fd S )Nc 4 j j p j j S r% )r enabledr& r s r z?SuiteRequirements.on_update_or_deferrable_fks..F s D*2 +"* r
r only_ifr s `r on_update_or_deferrable_fksz-SuiteRequirements.on_update_or_deferrable_fks@ s.
!
+
+
+
+
r
c ( t j S )z;Target database must support self-referential foreign keys.r r s r self_referential_foreign_keysz/SuiteRequirements.self_referential_foreign_keysJ r r
c ( t j S )z=Target database must support the DDL phrases for FOREIGN KEY.r r s r foreign_key_ddlz!SuiteRequirements.foreign_key_ddlP r r
c ( t j S )z3target database must support names for constraints.r r s r named_constraintsz#SuiteRequirements.named_constraintsV r r
c ( t j S )z(Target database must support subqueries.r r s r
subqueriesz SuiteRequirements.subqueries\ r r
c ( t j S )zRtarget database can render OFFSET, or an equivalent, in a
SELECT.
r r s r offsetzSuiteRequirements.offsetb r
c ( t j S )zWtarget database can render LIMIT and/or OFFSET using a bound
parameter
r r s r bound_limit_offsetz$SuiteRequirements.bound_limit_offsetj r9 r
c ( t j S )ztarget database can render LIMIT and/or OFFSET with a complete
SQL expression, such as one that uses the addition operator.
parameter
r r s r sql_expression_limit_offsetz-SuiteRequirements.sql_expression_limit_offsetr r
c ( t j S )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.
r r s r /parens_in_union_contained_select_w_limit_offsetzASuiteRequirements.parens_in_union_contained_select_w_limit_offset{ r
c ( t j 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 s r 0parens_in_union_contained_select_wo_limit_offsetzBSuiteRequirements.parens_in_union_contained_select_wo_limit_offset s r
c ( t j S )z;Target database must support boolean expressions as columnsr r s r boolean_col_expressionsz)SuiteRequirements.boolean_col_expressions r# r
c ( t j S )z5Target database allows boolean columns to store NULL.r r s r nullable_booleansz#SuiteRequirements.nullable_booleans r r
c ( t j S )z,Target backends that support nulls ordering.r r s r
nullsorderingz SuiteRequirements.nullsordering r# r
c ( t j S )ztarget database/driver supports bound parameters as column expressions
without being in the context of a typed column.
r r s r standalone_bindsz"SuiteRequirements.standalone_binds """r
c ( t j S )ztarget database/driver supports bound parameters with NULL in the
WHERE clause, in situations where it has to be typed.
r r s r !standalone_null_binds_whereclausez3SuiteRequirements.standalone_null_binds_whereclause r9 r
c ( t j S )z5Target database must support INTERSECT or equivalent.r r s r intersectzSuiteRequirements.intersect """r
c ( t j S )z?Target database must support EXCEPT or equivalent (i.e. MINUS).r r s r except_zSuiteRequirements.except_ rQ r
c ( t j S )z.Target database must support window functions.r r s r window_functionsz"SuiteRequirements.window_functions rQ r
c ( t j S )z Target database supports CTEsr r s r cteszSuiteRequirements.ctes r# r
c ( t j S )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 r s r ctes_with_update_deletez)SuiteRequirements.ctes_with_update_delete """r
c ( t j S )z}target database supports CTES which consist of INSERT, UPDATE
or DELETE *within* the CTE, e.g. WITH x AS (UPDATE....)r r s r ctes_on_dmlz SuiteRequirements.ctes_on_dml
"""r
c ( t j S )z~target platform generates new surrogate integer primary key values
when insert() is executed, excluding the pk column.r r s r autoincrement_insertz&SuiteRequirements.autoincrement_insert r r
c ( t j 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 s r fetch_rows_post_commitz(SuiteRequirements.fetch_rows_post_commit s r
c ( t j S )ztarget platform supports SQL expressions in GROUP BY
e.g.
SELECT x + y AS somelabel FROM table GROUP BY x + y
r r s r group_by_complex_expressionz-SuiteRequirements.group_by_complex_expression rA r
c . t j d d S )Nc & | j j j S r% )dbdialectsupports_sane_rowcountconfigs r r+ z1SuiteRequirements.sane_rowcount.. s vy 0 GG r
z&driver doesn't support 'sane' rowcountr skip_ifr s r
sane_rowcountz SuiteRequirements.sane_rowcount s ! G G 4
r
c . t j d d S )Nc & | j j j S r% )rf rg supports_sane_multi_rowcountri s r r+ z7SuiteRequirements.sane_multi_rowcount.. s vy 0 MM r
z;driver %(driver)s %(doesnt_support)s 'sane' multi row countr fails_ifr s r sane_multi_rowcountz%SuiteRequirements.sane_multi_rowcount s " M M I
r
c . t j d d S )Nc & | j j j S r% )rf rg supports_sane_rowcount_returningri s r r+ z=SuiteRequirements.sane_rowcount_w_returning..
s !B r
z;driver doesn't support 'sane' rowcount when returning is onrq r s r sane_rowcount_w_returningz+SuiteRequirements.sane_rowcount_w_returning
s' "
J
r
c . t j d d S )zatarget platform supports INSERT with no values, i.e.
INSERT DEFAULT VALUES or equivalent.c F | j j j p| j j j S r% )rf rg supports_empty_insertsupports_default_valuesri s r r+ z1SuiteRequirements.empty_inserts.. s! 69,B 9y 8 r
zempty inserts not supportedr, r s r
empty_insertsz SuiteRequirements.empty_inserts s&
!
9
9 )
r
c ( t j S )z.target platform supports INSERT from a SELECT.r r s r insert_from_selectz$SuiteRequirements.insert_from_select r r
c . t j d d S )z#target platform supports RETURNING.c $ | j j j S r% )rf rg implicit_returningri s r r+ z-SuiteRequirements.returning..) s 69,? r
z)%(database)s %(does_support)s 'returning'r, r s r returningzSuiteRequirements.returning$ s" ! ? ? 7
r
c ( t j S )zZTarget platform supports the syntax
"(x, y) IN ((x1, y1), (x2, y2), ...)"
r r s r tuple_inzSuiteRequirements.tuple_in- rL r
c | j S )z%Target platform tuple IN w/ empty set)r r s r tuple_in_w_emptyz"SuiteRequirements.tuple_in_w_empty5 s } r
c ( t j S )zwtarget platform supports a SELECT statement that has
the same name repeated more than once in the columns list.r r s r %duplicate_names_in_cursor_descriptionz7SuiteRequirements.duplicate_names_in_cursor_description: r r
c . t j d d S )z[Target database must have 'denormalized', i.e.
UPPERCASE as case insensitive names.c & | j j j S r% )rf rg requires_name_normalizeri s r r+ z6SuiteRequirements.denormalized_names..G s vy 0 HH r
z,Backend does not require denormalized names.rk r s r denormalized_namesz$SuiteRequirements.denormalized_namesA s"
! H H :
r
c . t j d d S )zTtarget database must support multiple VALUES clauses in an
INSERT statement.c & | j j j S r% )rf rg supports_multivalues_insertri s r r+ z7SuiteRequirements.multivalues_inserts..Q s vy 0 LL r
z*Backend does not support multirow inserts.rk r s r multivalues_insertsz%SuiteRequirements.multivalues_insertsK s"
! L L 8
r
c ( t j S )zvtarget dialect implements the executioncontext.get_lastrowid()
method without reliance on RETURNING.
r r s r implements_get_lastrowidz*SuiteRequirements.implements_get_lastrowidU r9 r
c ( t j 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 s r emulated_lastrowidz$SuiteRequirements.emulated_lastrowid] """r
c ( t j S )z]target platform includes a 'lastrowid' accessor on the DBAPI
cursor object.
r r s r dbapi_lastrowidz!SuiteRequirements.dbapi_lastrowidi rL r
c ( t j S )z#Target database must support VIEWs.r r s r viewszSuiteRequirements.viewsq r# r
c ( t j S )zXTarget database must support external schemas, and have one
named 'test_schema'.r r s r schemaszSuiteRequirements.schemasw r] r
c ( t j S )zJtarget system must support reflection of inter-schema foreign
keysr r s r cross_schema_fk_reflectionz,SuiteRequirements.cross_schema_fk_reflection~ r# r
c ( t j S )a Target supports refleciton of FOREIGN KEY constraints and
will return the name of the constraint that was used in the
"CONSTRANT FOREIGN KEY" DDL.
MySQL prior to version 8 and MariaDB prior to version 10.5
don't support this.
r r s r &foreign_key_constraint_name_reflectionz8SuiteRequirements.foreign_key_constraint_name_reflection r r
c ( t j S )ztarget system has a strong concept of 'default' schema that can
be referred to implicitly.
basically, PostgreSQL.
r r s r implicit_default_schemaz)SuiteRequirements.implicit_default_schema """r
c 0 t j d gd S )z0Target dialect must support server side cursors.c $ | j j j S r% )rf rg supports_server_side_cursorsri s r r+ z7SuiteRequirements.server_side_cursors.. s FI - J r
z no server side cursors supportr, r s r server_side_cursorsz%SuiteRequirements.server_side_cursors s% !
J
J K ,
r
c 0 t j d gd S )z'Target database must support SEQUENCEs.c $ | j j j S r% )rf rg supports_sequencesri s r r+ z-SuiteRequirements.sequences.. s FI - @ r
zno sequence supportr, r s r sequenceszSuiteRequirements.sequences s% !
@
@ A !
r
c 0 t j d gd S )zgTarget database supports sequences, but also optionally
as a means of generating new PK values.c F | j j j o| j j j S r% )rf rg r sequences_optionalri s r r+ z6SuiteRequirements.sequences_optional.. s! vy 0 C 9I%8 r
z.no sequence support, or sequences not optionalr, r s r r z$SuiteRequirements.sequences_optional s-
!9 9
=
r
c . t j d 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 $ | j j j S r% )rf rg postfetch_lastrowidri s r r+ z6SuiteRequirements.supports_lastrowid.. s FI - A r
r, r s r supports_lastrowidz$SuiteRequirements.supports_lastrowid s" !
A
A B
r
c 4 t j | j S )z"the opposite of supports_lastrowid)r NotPredicater r s r no_lastrowid_supportz&SuiteRequirements.no_lastrowid_support s &t'>???r
c ( t j S r% r r s r reflects_pk_namesz#SuiteRequirements.reflects_pk_names r' r
c ( t j S r% r r s r table_reflectionz"SuiteRequirements.table_reflection r
c ( t j S r% r r s r comment_reflectionz$SuiteRequirements.comment_reflection r' r
c | j S )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 r s r view_column_reflectionz(SuiteRequirements.view_column_reflection s zr
c | j S )zStarget database must support inspection of the full CREATE VIEW
definition.r r s r view_reflectionz!SuiteRequirements.view_reflection s zr
c | j S r% )r r s r schema_reflectionz#SuiteRequirements.schema_reflection s
|r
c ( t j S r% r r s r !primary_key_constraint_reflectionz3SuiteRequirements.primary_key_constraint_reflection r r
c ( t j S r% r r s r !foreign_key_constraint_reflectionz3SuiteRequirements.foreign_key_constraint_reflection r r
c ( t j S r% r r s r 1foreign_key_constraint_option_reflection_ondeletezCSuiteRequirements.foreign_key_constraint_option_reflection_ondelete r' r
c ( t j S r% r r s r 1foreign_key_constraint_option_reflection_onupdatezCSuiteRequirements.foreign_key_constraint_option_reflection_onupdate r' r
c ( t j S r% r r s r temp_table_reflectionz'SuiteRequirements.temp_table_reflection r r
c ( t j S )z8target dialect supports listing of temporary table namesr r s r temp_table_namesz"SuiteRequirements.temp_table_names rQ r
c ( t j S )z)target database supports temporary tablesr r s r temporary_tablesz"SuiteRequirements.temporary_tables r
c ( t j S )z(target database supports temporary viewsr r s r temporary_viewsz!SuiteRequirements.temporary_views rQ r
c ( t j S r% r r s r index_reflectionz"SuiteRequirements.index_reflection r r
c ( t j S )z?target database supports CREATE INDEX with per-column ASC/DESC.r r s r indexes_with_ascdescz&SuiteRequirements.indexes_with_ascdesc r r
c ( t j S )z>target database supports CREATE INDEX against SQL expressions.r r s r indexes_with_expressionsz*SuiteRequirements.indexes_with_expressions rQ r
c ( t j S )z8target dialect supports reflection of unique constraintsr r s r unique_constraint_reflectionz.SuiteRequirements.unique_constraint_reflection r r
c ( t j S )z7target dialect supports reflection of check constraintsr r s r check_constraint_reflectionz-SuiteRequirements.check_constraint_reflection! rQ r
c ( t j S )ztarget dialect raises IntegrityError when reporting an INSERT
with a primary key violation. (hint: it should)
r r s r $duplicate_key_raises_integrity_errorz6SuiteRequirements.duplicate_key_raises_integrity_error& r9 r
c ( t j S )z3Target database must support VARCHAR with no lengthr r s r unbounded_varcharz#SuiteRequirements.unbounded_varchar. r r
c ( t j S )zTarget database/dialect must support Python unicode objects with
non-ASCII characters represented, delivered as bound parameters
as well as in result rows.
r r s r unicode_dataz SuiteRequirements.unicode_data4 r> r
c ( t j S )zRTarget driver must support some degree of non-ascii symbol
names.
r r s r unicode_ddlz SuiteRequirements.unicode_ddl= r] r
c ( t j S )z?Target driver can create tables with a name like 'some " table'r r s r symbol_names_w_double_quotez-SuiteRequirements.symbol_names_w_double_quoteD r r
c ( t j S )ztarget dialect supports rendering of a date, time, or datetime as a
literal string, e.g. via the TypeEngine.literal_processor() method.
r r s r datetime_literalsz#SuiteRequirements.datetime_literalsI rZ r
c ( t j S )zUtarget dialect supports representation of Python
datetime.datetime() objects.r r s r datetimezSuiteRequirements.datetimeR r r
c ( t j S )zftarget dialect supports representation of Python
datetime.datetime() with microsecond objects.r r s r datetime_microsecondsz'SuiteRequirements.datetime_microsecondsY r r
c ( t j S )ztarget dialect supports representation of Python
datetime.datetime() with microsecond objects but only
if TIMESTAMP is used.r r s r timestamp_microsecondsz(SuiteRequirements.timestamp_microseconds` r] r
c ( t j S zutarget dialect supports representation of Python
datetime.datetime() objects with historic (pre 1970) values.r r s r datetime_historicz#SuiteRequirements.datetime_historicg r] r
c ( t j S )zQtarget dialect supports representation of Python
datetime.date() objects.r r s r datezSuiteRequirements.daten r r
c ( t j S )zPtarget dialect accepts a datetime object as the target
of a date column.r r s r date_coerces_from_datetimez,SuiteRequirements.date_coerces_from_datetimeu r r
c ( t j S r r r s r
date_historicz SuiteRequirements.date_historic| r] r
c ( t j S )zQtarget dialect supports representation of Python
datetime.time() objects.r r s r timezSuiteRequirements.time r r
c ( t j S )zbtarget dialect supports representation of Python
datetime.time() with microsecond objects.r r s r time_microsecondsz#SuiteRequirements.time_microseconds r r
c ( t j S )zttarget database/driver can allow BLOB/BINARY fields to be compared
against a bound parameter value.
r r s r binary_comparisonsz$SuiteRequirements.binary_comparisons r9 r
c ( t j 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 s r binary_literalsz!SuiteRequirements.binary_literals r
c ( t j S )z:target dialect supports 'AUTOCOMMIT' as an isolation_levelr r s r
autocommitz SuiteRequirements.autocommit rQ r
c ( t j S )ztarget dialect supports general isolation level settings.
Note that this requirement, when enabled, also requires that
the get_isolation_levels() method be implemented.
r r s r isolation_levelz!SuiteRequirements.isolation_level r r
c 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_COMMITED",
"supported": [
"SERIALIZABLE", "READ UNCOMMITTED",
"READ COMMITTED", "REPEATABLE READ",
"AUTOCOMMIT"
]
}
Nr r rj s r get_isolation_levelsz&SuiteRequirements.get_isolation_levels s r
c ( t j S )z.target platform implements a native JSON type.r r s r json_typezSuiteRequirements.json_type r# r
c | j S )zNtarget platform supports numeric array indexes
within a JSON structure)r
r s r json_array_indexesz$SuiteRequirements.json_array_indexes s
~ r
c ( t j S r% r r s r (json_index_supplementary_unicode_elementz:SuiteRequirements.json_index_supplementary_unicode_element r r
c ( t j S )zRtarget backend has general support for moderately high-precision
numerics.r r s r precision_numerics_generalz,SuiteRequirements.precision_numerics_general r r
c ( t j S )zbtarget backend supports Decimal() objects using E notation
to represent very small values.r r s r "precision_numerics_enotation_smallz4SuiteRequirements.precision_numerics_enotation_small r# r
c ( t j S )zbtarget backend supports Decimal() objects using E notation
to represent very large values.r r s r "precision_numerics_enotation_largez4SuiteRequirements.precision_numerics_enotation_large r# r
c ( t j S )ztarget backend supports values with many digits on both sides,
such as 319438950232418390.273596, 87673.594069654243
r r s r *precision_numerics_many_significant_digitsz r
c ( t j S )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.
r r s r fetch_null_from_numericz)SuiteRequirements.fetch_null_from_numeric; r
c ( t j S )zUTarget database must support an unbounded Text() "
"type such as TEXT or CLOBr r s r text_typezSuiteRequirements.text_typeE r r
c ( t j S )zTtarget database can persist/return an empty string with a
varchar.
r r s r empty_strings_varcharz'SuiteRequirements.empty_strings_varcharL r9 r
c ( t j S )zRtarget database can persist/return an empty string with an
unbounded text.r r s r empty_strings_textz$SuiteRequirements.empty_strings_textT r r
c ( t j S )zUtarget database supports use of an unbounded textual field in a
WHERE clause.r r s r "expressions_against_unbounded_textz4SuiteRequirements.expressions_against_unbounded_text[ r r
c ( t j S )z;target driver must support the literal statement 'select 1'r r s r selectonezSuiteRequirements.selectoneb r r
c ( t j S )z(Target database must support savepoints.r r s r
savepointsz SuiteRequirements.savepointsg r# r
c ( t j S )z4Target database must support two-phase transactions.r r s r two_phase_transactionsz(SuiteRequirements.two_phase_transactionsm r# r
c ( t j S )z'Target must support UPDATE..FROM syntaxr r s r update_fromz SuiteRequirements.update_froms rQ r
c ( t j S )z=Target must support DELETE FROM..FROM or DELETE..USING syntaxr r s r delete_fromz SuiteRequirements.delete_fromx rQ r
c ( t j 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 s r update_where_target_in_subqueryz1SuiteRequirements.update_where_target_in_subquery} r r
c ( t j S )zOtarget database must use a plain percent '%' as the 'modulus'
operator.r r s r mod_operator_as_percent_signz.SuiteRequirements.mod_operator_as_percent_sign r# r
c ( t j 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 s r percent_schema_namesz&SuiteRequirements.percent_schema_names r r
c ( t j S )ztarget 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 s r order_by_col_from_unionz)SuiteRequirements.order_by_col_from_union r% r
c ( t j 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 s r order_by_label_with_expressionz0SuiteRequirements.order_by_label_with_expression s """r
c 6 fd}t j | S )Nc V | dS # t $ r Y dS w xY w)NFT)get_order_by_collationNotImplementedError)rj r s r checkz3SuiteRequirements.order_by_collation..check sC
++F333 u&
tt
s
((rk )r rF s ` r order_by_collationz$SuiteRequirements.order_by_collation s/ !%(((r
c t r% )rE r s r rD z(SuiteRequirements.get_order_by_collation s !###r
c ( t j S )zUTarget driver must support non-ASCII characters being passed at
all.
r r s r unicode_connectionsz%SuiteRequirements.unicode_connections r r
c ( t j S )zTarget 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 s r graceful_disconnectsz&SuiteRequirements.graceful_disconnects r9 r
c ( t j S )zU
Target must support simultaneous, independent database connections.
r r s r independent_connectionsz)SuiteRequirements.independent_connections r r
c ( t j S )z9Catchall for a large variety of MySQL on Windows failuresr r s r skip_mysql_on_windowsz'SuiteRequirements.skip_mysql_on_windows r r
c , t j d 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 | j j S r% )optionslow_connectionsri s r r+ z2SuiteRequirements.ad_hoc_engines.. s 6>9 r
rk r s r ad_hoc_enginesz SuiteRequirements.ad_hoc_engines s ! 9 9
r
c * t j d S )Ntiming_intensiver requires_tagr s r rW z"SuiteRequirements.timing_intensive &'9:::r
c * t j d S )Nmemory_intensiverX r s r r\ z"SuiteRequirements.memory_intensive rZ r
c . t j d d S )zMark tests that use threading and mock at the same time - stability
issues have been observed with coverage + python 3.3
c 2 t j o | j j S r% )r py3krS has_coverageri s r r+ z7SuiteRequirements.threading_with_mock.. s 49D )D r
z%Stability issues with coverage + py3krk r s r threading_with_mockz%SuiteRequirements.threading_with_mock s" ! D D 3
r
c . t j d d S )Nc " t j dk S N) sys version_infor r
r r+ z+SuiteRequirements.python2.. s C$, r
z Python version 2.xx is required.rk r s r python2zSuiteRequirements.python2 s ! , , .
r
c . t j d d S )Nc " t j dk S rd rf r r
r r+ z+SuiteRequirements.python3.. s C$t+ r
z Python version 3.xx is required.rk r s r python3zSuiteRequirements.python3 s ! + +-O
r
c | j S r% )python36r s r pep520zSuiteRequirements.pep520 s
} r
c . t j d d S )Nc " t j dk S )N)re rf r r
r r+ z,SuiteRequirements.python36.. C$v- r
z*Python version 3.6 or greater is required.rk r s r rn zSuiteRequirements.python36 ! - - 8
r
c . t j d d S )Nc " t j dk S )N)re rf r r
r r+ z,SuiteRequirements.python37.. rs r
z*Python version 3.7 or greater is required.rk r s r python37zSuiteRequirements.python37 rt r
c . t j d d S )Nc t j S r% )r cpythonr r
r r+ z+SuiteRequirements.cpython..# s DL r
zcPython interpreter neededr, r s r r{ zSuiteRequirements.cpython s ! ">
r
c @ ddl m t j fdd S )Nr picklec T t j r j dk pt j dk S )NcPickle)re r )r pypyr rg rh r} s r r+ z5SuiteRequirements.non_broken_pickle..+ s- M -9,* 6) r
z.Needs cPickle+cPython or newer Python 3 pickle)sqlalchemy.utilr~ r r- )r r~ s @r non_broken_picklez#SuiteRequirements.non_broken_pickle& sC ******!
*
*
*
*
=
r
c | j S )ztarget platform must remove all cycles unconditionally when
gc.collect() is called, as well as clean out unreferenced subclasses.
)r{ r s r predictable_gcz SuiteRequirements.predictable_gc1 s |r
c . t j d d S )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 | j j S r% )rS r` ri s r r+ z/SuiteRequirements.no_coverage..B s 6>6 r
z(Issues observed when coverage is enabledrk r s r no_coveragez SuiteRequirements.no_coverage9 s" ! 6 6 6
r
c dS NFr r s r _has_mysql_on_windowsz'SuiteRequirements._has_mysql_on_windowsF ur
c dS r r r s r _has_mysql_fully_case_sensitivez1SuiteRequirements._has_mysql_fully_case_sensitiveI r r
c 2 t j fd S )Nc . S r% ) _has_sqliter s r r+ z*SuiteRequirements.sqlite..N s d.>.>.@.@*@ r
rk r s `r sqlitezSuiteRequirements.sqliteL s !"@"@"@"@AAAr
c 4 t j fdd S )Nc . S r% )_has_cextensionsr s r r+ z/SuiteRequirements.cextensions..S s --/// r
zC extensions not installedrk r s `r cextensionsz SuiteRequirements.cextensionsP s' ! / / / /1M
r
c L ddl m} |d dS # t $ r Y dS w xY w)Nr )
create_enginez sqlite://TF)
sqlalchemyr ImportError)r r s r r z SuiteRequirements._has_sqliteV sP ,,,,,, M+ & & &4 55 s
##c : ddl m}m} dS # t $ r Y dS w xY w)Nr ) cresultproxy cprocessorsTF)r r r r )r r r s r r z"SuiteRequirements._has_cextensions_ sF < < < < < < < <4 55 s
c ( t j S )zSupports computed columnsr r s r computed_columnsz"SuiteRequirements.computed_columnsg rQ r
c ( t j S )z/Supports computed columns with `persisted=True`r r s r computed_columns_storedz)SuiteRequirements.computed_columns_storedl rQ r
c ( t j S )z0Supports computed columns with `persisted=False`r r s r computed_columns_virtualz*SuiteRequirements.computed_columns_virtualq rQ r
c ( t j S )zSIf the default persistence is virtual or stored when `persisted`
is omittedr r s r "computed_columns_default_persistedz4SuiteRequirements.computed_columns_default_persistedv r# r
c ( t j S )zTIf persistence information is returned by the reflection of
computed columnsr r s r "computed_columns_reflect_persistedz4SuiteRequirements.computed_columns_reflect_persisted| r# r
c . t j d 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 & | j j j S r% )rf rg supports_is_distinct_fromri s r r+ z=SuiteRequirements.supports_is_distinct_from.. s vy 0 JJ r
z4driver doesn't support an IS DISTINCT FROM constructrk r s r r z+SuiteRequirements.supports_is_distinct_from s" ! J J B
r
N)r r
r propertyr r r r r" r& r. r0 r2 r4 r6 r8 r; r= r@ rC rE rG rI rK rN rP rS rU rW rY r\ r_ ra rc rm rs rw 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/ r1 r3 r5 r7 r9 r; r= r? rA rG rD rJ rL rN rP rU rW r\ ra ri rl ro rn rx r{ r r r r r r r r r r r r r r r r r
r r r s
! ! X!
! ! X!
! ! X!
! ! X! # # X#
# # X#
X
! ! X!
! ! X!
! ! X!
! ! X!
! ! X! ! ! X! ! ! X! ! ! X ! ! ! X ! # # X#
! ! X!
# # X#
# # X# ! ! X! # # X# # # X# # # X# # # X#
# # X# # # X# ! ! X!
!
! X
! ! ! X !
X
X
X
X
! ! X!
X
# # X# X ! ! X!
X
X
! ! X! # # X # # # X# # # X#
# # X# # # X#
# # X # # # X#
X
X
X
X
@ @ X@ # # X# ! ! X! # # X# X X
X ! ! X! ! ! X! # # X# # # X# ! ! X! # # X# ! ! X! # # X# ! ! X! ! ! X! # # X# ! ! X! # # X# ! ! X! ! ! X!
! ! X! # # X# ! ! X! # # X# ! ! X! ! ! X! # # X# # # X# ! ! X! ! ! X! # # X# ! ! X! ! ! X! ! ! X!
!
! X
! # # X# # # X# 4 # # X#
X ! ! X! ! ! X!
# # X#
# # X#
# # X# ! ! X!( ! ! X! ! ! X! # # X# ! ! X! ! ! X! ! ! X! ! ! X! ! ! X! ! ! X! ! ! X! ! ! X! # # X#
# # X#
# # X# # # X#
!
! X
! # # X#
# # X # ! ! X! # # X # ) ) X)$ $ $ ! ! X! ! ! X! ! ! X! ! ! X!
X
; ; X; ; ; X;
X
X
X
X
X
X
X
X
X
X
B B XB
X
# # X# # # X# # # X# # # X#
# # X#
X
r
r )__doc__rg r r objectr r r r
r r s
6 t
t
t
t
t
t
t
t
t
t
r