[ https://issues.apache.org/jira/browse/DDLUTILS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Dudziak updated DDLUTILS-208: ------------------------------------ Component/s: (was: Core - PostgreSql) Fix Version/s: (was: 1.1) 1.3 Summary: Recreating a database does not start the new sequence at the value of the old table (was: PostgreSQL: RecreateTableChange loses autoIncrement) > Recreating a database does not start the new sequence at the value of the old > table > ----------------------------------------------------------------------------------- > > Key: DDLUTILS-208 > URL: https://issues.apache.org/jira/browse/DDLUTILS-208 > Project: DdlUtils > Issue Type: Bug > Components: Core (No specific database) > Environment: PostgreSQL 8.3.1 > Reporter: Rijk van Haaften > Assignee: Thomas Dudziak > Fix For: 1.3 > > > PlatformImplBase.processChange(RecreateTableChange) does not migrate > (autoincrement) sequences, but does call SqlBuilder.dropTables. > PostgreSqlBuilder.dropTables explicitly drops the sequences: > for (int idx = 0; idx < columns.length; idx++) > { > dropAutoIncrementSequence(table, columns[idx]); > } > (On the other hand, HsqlDbBuilder does not drop the sequence for instance.) > The sequence is created again, but that causes 'duplicate' errors on the > column using the sequence. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.