|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
public interface MySQLVendor
This is vendor for MySQL database. MySQL typically does not understand schema-qualified names, so this vendor doesn't process any schema name it encounters when creating a SQL string.
| Method Summary | |
|---|---|
boolean |
legacyLimit()
Returns whether the legacy LIMIT expression is used instead of the of the newer LIMIT/OFFSET. |
void |
setLegacyLimit(boolean useLegacyLimit)
Sets the switch to use legacy LIMIT expression instead of the newer LIMIT/OFFSET expressions. |
| Methods inherited from interface org.sql.generation.api.vendor.SQLVendor |
|---|
getBooleanFactory, getColumnsFactory, getDataTypeFactory, getDefinitionFactory, getLiteralFactory, getManipulationFactory, getModificationFactory, getQueryFactory, getTableReferenceFactory, toString |
| Method Detail |
|---|
boolean legacyLimit()
Returns whether the legacy LIMIT expression is used instead of the of the newer LIMIT/OFFSET. In a legacy syntax,
the LIMIT <n> OFFSET <skip> is written as LIMIT <skip>, <n> instead. This method is not
thread-safe.
true if the legacy LIMIT expressions are used; false otherwise.void setLegacyLimit(boolean useLegacyLimit)
Sets the switch to use legacy LIMIT expression instead of the newer LIMIT/OFFSET expressions. In a legacy syntax,
the LIMIT <n> OFFSET <skip> is written as LIMIT <skip>, <n> instead. Set this to true only if
you really require it. This method is not thread-safe.
useLegacyLimit - Whether to use legacy LIMIT expression instead of the newer LIMIT/OFFSET expressions.
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||