[
https://issues.apache.org/jira/browse/DDLUTILS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Dudziak resolved DDLUTILS-134.
-------------------------------------
Resolution: Invalid
DdlUtils can insert data into auto-increment columns in two ways:
* using the value defined in the row to insert thereby effectively overriding
the auto-increment value
* using the auto-increment value which ignoresany value in the row
The latter is the default as the first option won't change the auto-increment
sequence (whether internal or DdlUtils-created) and hence a later insertion of
data using the second option might lead to conflicts if unique values are
required.
In order to use option 1 via the Ant tasks, one has to set the
useExplicitIdentityValues parameter to true
(http://db.apache.org/ddlutils/ant/org.apache.ddlutils.task.WriteDataToDatabaseCommand.html#parameter-useexplicitidentityvalues).
> Bad start value when importing identity in Derby
> ------------------------------------------------
>
> Key: DDLUTILS-134
> URL: https://issues.apache.org/jira/browse/DDLUTILS-134
> Project: DdlUtils
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: PostgreSQL 8.1.4; Derby 10.2.1
> Reporter: Laurent ROCHE
> Assigned To: Thomas Dudziak
> Attachments: Ddlutils-test.zip, my_build.xml, test_derby.sql
>
>
> I am transfering a DB from PostgreSQL to Derby using DDL-Utils Ant program.
> I have columns defines as SERIAL and with data in PostgreSQL and when
> transfered the start value for the serial colum is ONE (in Derby) when I
> would expect it to be the same as in Postgres (the increment value seems
> strange too).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
