| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| public boolean | dropConstraints()
ASA does not require to drop constraint before dropping tables, so disable it.
|
| public IdentityColumnSupport | getIdentityColumnSupport()
Overrides org. IdentityColumnSupport
|
| public String | getNoColumnsInsertString()
Overrides org. The fragment used to insert a row without specifying any column values. |
| protected SqlTypeDescriptor | getSqlTypeDescriptorOverride(int
A sqlCode)Types constant indicating the SQL column typeOverrides org. SqlTypeDescriptor that should be used to handle the given JDBC type code.
|
| SybaseAnywhereDialect | back to summary |
|---|---|
| public SybaseAnywhereDialect() | |
| dropConstraints | back to summary |
|---|---|
| public boolean dropConstraints() Overrides org. Doc from org. ASA does not require to drop constraint before dropping tables, so disable it. NOTE : Also, the DROP statement syntax used by Hibernate to drop constraints is not compatible with ASA. Do we need to drop constraints before dropping tables in this dialect?
| |
| getIdentityColumnSupport | back to summary |
|---|---|
| public IdentityColumnSupport getIdentityColumnSupport() Overrides org. Doc from org. Get the appropriate
| |
| getNoColumnsInsertString | back to summary |
|---|---|
| public String getNoColumnsInsertString() Overrides org. Doc from org. Sybase Anywhere syntax would require a "DEFAULT" for each column specified, but I suppose Hibernate use this syntax only with tables with just 1 column The fragment used to insert a row without specifying any column values. This is not possible on some databases. | |
| getSqlTypeDescriptorOverride | back to summary |
|---|---|
| protected SqlTypeDescriptor getSqlTypeDescriptorOverride(int sqlCode) Overrides org. Doc from org. Returns the
| |