This defines the syntax for adding a column in an alter.
This defines the syntax for adding a column in an alter. This is used because some DBs (Oracle, for one) use slightly different syntax.
Whether this database supports LIMIT clause in SELECTs.
Whether this database supports LIMIT clause in SELECTs.
Allow the driver to do specific remapping of column types for cases where not all types are supported.
Allow the driver to do specific remapping of column types for cases where not all types are supported. Classes that want to do custom type mapping for columns should override the customColumnTypeMap method.
Allows the Vendor-specific Driver to do custom type mapping for a particular column type.
Allows the Vendor-specific Driver to do custom type mapping for a particular column type.
Name of the default db schema.
Name of the default db schema. If not set, then the schema is assumed to equal the db user name.
Maximum value of the LIMIT clause in SELECT.
Maximum value of the LIMIT clause in SELECT.
Performs an insert and optionally returns the ResultSet of the generated keys that were inserted.
Performs an insert and optionally returns the ResultSet of the generated keys that were inserted. If no keys are specified, return the number of rows updated.
A connection that the method can optionally use if it needs to execute ancillary statements
The prepared query string to use for the insert
A function that will set the parameters on the prepared statement
Whether the primary key has been defined by the index column.
Whether the primary key has been defined by the index column. H2 creates primary key for a table, when AUTO_INCREMENT type is used. <--- NOT TRUE I went into the H2 console, created a table with auto_increment and was able to insert duplicate ids. Then I created it with AUTO_INCREMENT PRIMARY KEY and it did not allow it.
This method can be overriden by DriverType impls to allow for custom setup of Primary Key Columns (creating sequeneces or special indices, for example).
This method can be overriden by DriverType impls to allow for custom setup of Primary Key Columns (creating sequeneces or special indices, for example). The List of commands will be executed in order.
This indicates that Schemifier needs to run with a non-transacted connection.
This indicates that Schemifier needs to run with a non-transacted connection. Certain databases require that gathering information on tables (which Schemifier uses for updates) run outside of a transaction.
This specifies that the driver supports FKs in tables.
This specifies that the driver supports FKs in tables. Note that to enable FK generation in Schemifier, you also need to set MapperRules.createForeignKeys_? to true before running it.