[
https://issues.apache.org/jira/browse/DERBY-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin D. closed DERBY-4452.
----------------------------
Resolution: Not A Problem
The documentation has been updated to reflect the mentioned behavior.
> Enhance docs to clarify handling of internal id counter for generated by
> default keys
> -------------------------------------------------------------------------------------
>
> Key: DERBY-4452
> URL: https://issues.apache.org/jira/browse/DERBY-4452
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.5.3.0
> Environment: derby 10.5.3.0, jdbc, embedded db
> Reporter: Martin D.
> Priority: Minor
>
> it seem that the internal auto id counter for generating the keys (ids) is
> not updated when a value with a fix id is inserted.
> sample code:
> try {
> Connection con =
> DriverManager.getConnection("jdbc:derby:db/data/tmp;create=true");
> Statement stmt = con.createStatement();
> stmt.executeUpdate(
> "CREATE TABLE testtable (id INTEGER NOT NULL GENERATED BY
> DEFAULT AS IDENTITY, value INT NOT NULL, PRIMARY KEY(ID))");
> // insert a few test values with auto id
> stmt.execute("INSERT INTO testtable (value) VALUES (1),(2),(3)");
> // insert more values with fix id
> stmt.execute("INSERT INTO testtable (id,value) VALUES
> (4,4),(5,5),(6,6)");
> // try to insert more values with auto id
> // -> will throw SQLIntegrityConstraintViolationException (SQLState
> 23505)
> stmt.execute("INSERT INTO testtable (value) VALUES (7)");
> stmt.close();
> con.close();
> } catch (Exception e) {
> e.printStackTrace();
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
