spring-framework / org.springframework.jdbc.support.incrementer / SybaseMaxValueIncrementer

SybaseMaxValueIncrementer

open class SybaseMaxValueIncrementer : AbstractIdentityColumnMaxValueIncrementer

DataFieldMaxValueIncrementer that increments the maximum value of a given Sybase table with the equivalent of an auto-increment column. Note: If you use this class, your table key column should NOT be defined as an IDENTITY column, as the sequence table does the job.

This class is intended to be used with Sybase Adaptive Server.

The sequence is kept in a table. There should be one sequence table per table that needs an auto-generated key.

Example:

create table tab (id int not null primary key, text varchar(100)) create table tab_sequence (id bigint identity) insert into tab_sequence values()
If "cacheSize" is set, the intermediate values are served without querying the database. If the server or your application is stopped or crashes or a transaction is rolled back, the unused values will never be served. The maximum hole size in numbering is consequently the value of cacheSize. HINT: Since Sybase supports the JDBC 3.0 getGeneratedKeys method, it is recommended to use IDENTITY columns directly in the tables and then using a org.springframework.jdbc.core.simple.SimpleJdbcInsert or utilizing a org.springframework.jdbc.support.KeyHolder when calling the with the update(PreparedStatementCreator psc, KeyHolder generatedKeyHolder) method of the org.springframework.jdbc.core.JdbcTemplate.

Thanks to Yinwei Liu for the suggestion!

Author
Thomas Risberg

Author
Juergen Hoeller

Since
2.5.5

Constructors

<init>

SybaseMaxValueIncrementer()

Default constructor for bean property style usage.

SybaseMaxValueIncrementer(dataSource: DataSource, incrementerName: String, columnName: String)

Convenience constructor.

Inherited Functions

isDeleteSpecificValues

open fun isDeleteSpecificValues(): Boolean

Return whether to delete the entire range below the current maximum key value (false - the default), or the specifically generated values (true).

setDeleteSpecificValues

open fun setDeleteSpecificValues(deleteSpecificValues: Boolean): Unit

Specify whether to delete the entire range below the current maximum key value (false - the default), or the specifically generated values (true). The former mode will use a where range clause whereas the latter will use an in clause starting with the lowest value minus 1, just preserving the maximum value.

Inheritors

SybaseAnywhereMaxValueIncrementer

open class SybaseAnywhereMaxValueIncrementer : SybaseMaxValueIncrementer

DataFieldMaxValueIncrementer that increments the maximum value of a given Sybase SQL Anywhere table with the equivalent of an auto-increment column. Note: If you use this class, your table key column should NOT be defined as an IDENTITY column, as the sequence table does the job.

This class is intended to be used with Sybase Anywhere.

The sequence is kept in a table. There should be one sequence table per table that needs an auto-generated key.

Example:

create table tab (id int not null primary key, text varchar(100)) create table tab_sequence (id bigint identity) insert into tab_sequence values(DEFAULT)
If "cacheSize" is set, the intermediate values are served without querying the database. If the server or your application is stopped or crashes or a transaction is rolled back, the unused values will never be served. The maximum hole size in numbering is consequently the value of cacheSize. HINT: Since Sybase Anywhere supports the JDBC 3.0 getGeneratedKeys method, it is recommended to use IDENTITY columns directly in the tables and then using a org.springframework.jdbc.core.simple.SimpleJdbcInsert or utilizing a org.springframework.jdbc.support.KeyHolder when calling the with the update(PreparedStatementCreator psc, KeyHolder generatedKeyHolder) method of the org.springframework.jdbc.core.JdbcTemplate.

Thanks to Tarald Saxi Stormark for the suggestion!