SQLAlchemy 0.3 Documentation
- Module Functions
- class OracleBinary(Binary)
- class OracleBoolean(Boolean)
- class OracleChar(CHAR)
- class OracleCompiler(ANSICompiler)
- class OracleDateTime(DateTime)
- class OracleDefaultRunner(ANSIDefaultRunner)
- class OracleDialect(ANSIDialect)
- class OracleDialect(ANSIDialect)
- class OracleExecutionContext(DefaultExecutionContext)
- class OracleInteger(Integer)
- class OracleNumeric(Numeric)
- class OracleRaw(Binary)
- class OracleSchemaDropper(ANSISchemaDropper)
- class OracleSchemaGenerator(ANSISchemaGenerator)
- class OracleSmallInteger(SmallInteger)
- class OracleString(String)
- class OracleText(TEXT)
- class OracleTimestamp(DateTime)
module sqlalchemy.databases.oracle
class OracleBinary(Binary)
back to section topclass OracleBoolean(Boolean)
back to section topclass OracleCompiler(ANSICompiler)
Oracle compiler modifies the lexical structure of Select statements to work under non-ANSI configured Oracle databases, if the use_ansi flag is False.
Called when a SELECT statement has no froms, and no FROM clause is to be appended.
The Oracle compiler tacks a "FROM DUAL" to the statement.
INSERT s are required to have the primary keys be explicitly present.
Mapper will by default not put them in the insert statement to comply with autoincrement fields that require they not be present. so, put them all in for all primary key columns.
This is the sequence equivalent to ANSICompiler's visit_insert_column_default which ensures that the column is present in the generated column list.
Look for LIMIT and OFFSET in a select statement, and if so tries to wrap it in a subquery with row_number() criterion.