"Computed columns don't work with Oracle Database UPDATE "
"statements that use RETURNING; the value of the column "
"*before* the UPDATE takes place is returned. It is "
- "advised to not use RETURNING with an Oracle Database computed "
- "column. Consider setting implicit_returning to False on "
- "the Table object in order to avoid implicit RETURNING "
- "clauses from being generated for this Table."
+ "advised to not use RETURNING with an Oracle Database "
+ "computed "column. Consider setting implicit_returning "
+ "to False on "the Table object in order to avoid implicit "
+ "RETURNING clauses from being generated for this Table."
)
if column.type._has_column_expression:
col_expr = column.type.column_expression(column)
)
if generated.persisted is True:
raise exc.CompileError(
- "Oracle Database computed columns do not support 'stored' persistence; "
- "set the 'persisted' flag to None or False for Oracle Database support."
+ "Oracle Database computed columns do not support 'stored' "
+ "persistence; set the 'persisted' flag to None or False for "
+ "Oracle Database support."
)
elif generated.persisted is False:
text += " VIRTUAL"
r"""
Construct a FLOAT
- :param binary_precision: Oracle Database binary precision value to be rendered
- in DDL. This may be approximated to the number of decimal characters
- using the formula "decimal precision = 0.30103 * binary precision".
- The default value used by Oracle Database for FLOAT / DOUBLE PRECISION is 126.
+ :param binary_precision: Oracle Database binary precision value to be
+ rendered in DDL. This may be approximated to the number of decimal
+ characters using the formula "decimal precision = 0.30103 * binary
+ precision". The default value used by Oracle Database for FLOAT /
+ DOUBLE PRECISION is 126.
:param asdecimal: See :paramref:`_sqltypes.Float.asdecimal`
use Oracle Database's ``TIMESTAMP WITH TIME ZONE`` datatype.
:param local_timezone: boolean. Indicates that the TIMESTAMP type
- should use Oracle Database's ``TIMESTAMP WITH LOCAL TIME ZONE`` datatype.
+ should use Oracle Database's ``TIMESTAMP WITH LOCAL TIME ZONE``
+ datatype.
"""
The setinputsizes hook overall is only used for dialects which include
the flag ``use_setinputsizes=True``. Dialects which use this
- include python-oracledb, cx_Oracle, pg8000, asyncpg, and pyodbc dialects.
+ include python-oracledb, cx_Oracle, pg8000, asyncpg, and pyodbc
+ dialects.
.. note::
@compiles(coalesce, 'oracle')
def compile(element, compiler, **kw):
if len(element.clauses) > 2:
- raise TypeError("coalesce only supports two arguments on Oracle Database")
+ raise TypeError("coalesce only supports two arguments on "
+ "Oracle Database")
return "nvl(%s)" % compiler.process(element.clauses, **kw)
* :class:`.ExecutableDDLElement` - The root of all DDL expressions,
statement._label_style = self.label_style
# Oracle Database however does not allow FOR UPDATE on the subquery,
- # and the Oracle Database dialects ignore it, plus for PostgreSQL, MySQL
- # we expect that all elements of the row are locked, so also put it
- # on the outside (except in the case of PG when OF is used)
+ # and the Oracle Database dialects ignore it, plus for PostgreSQL,
+ # MySQL we expect that all elements of the row are locked, so also put
+ # it on the outside (except in the case of PG when OF is used)
if (
self._for_update_arg is not None
and self._for_update_arg.of is None
"""Called when a SELECT statement has no froms, and no FROM clause is
to be appended.
- Gives Oracle Database a chance to tack on a ``FROM DUAL`` to the string output.
+ Gives Oracle Database a chance to tack on a ``FROM DUAL`` to the string
+ output.
"""
return ""
the operator as "REGEXP" or "NOT REGEXP". This is compatible with
SQLite and MySQL, for example.
- Regular expression support is currently implemented for Oracle Database,
- PostgreSQL, MySQL and MariaDB. Partial support is available for
- SQLite. Support among third-party dialects may vary.
+ Regular expression support is currently implemented for Oracle
+ Database, PostgreSQL, MySQL and MariaDB. Partial support is available
+ for SQLite. Support among third-party dialects may vary.
:param pattern: The regular expression pattern string or column
clause.
understood by Oracle Database and PostgreSQL.
:param order: optional boolean value; if ``True``, renders the
- ORDER keyword, understood by Oracle Database, indicating the sequence is
- definitively ordered. May be necessary to provide deterministic
+ ORDER keyword, understood by Oracle Database, indicating the sequence
+ is definitively ordered. May be necessary to provide deterministic
ordering using Oracle RAC.
:param data_type: The type to be returned by the sequence, for
**specific to a single table** to a statement, in a location that
is **dialect-specific**. To add generic optimizer hints to the
**beginning** of a statement ahead of the SELECT keyword such as
- for MySQL or Oracle Database, use the :meth:`_expression.Select.prefix_with`
- method. To add optimizer hints to the **end** of a statement such
- as for PostgreSQL, use the
+ for MySQL or Oracle Database, use the
+ :meth:`_expression.Select.prefix_with` method. To add optimizer
+ hints to the **end** of a statement such as for PostgreSQL, use the
:meth:`_expression.Select.with_statement_hint` method.
The text of the hint is rendered in the appropriate