[DDLUTILS-208] Recreating a database does not start the new sequence at the value of the old table

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 1.3
• Component/s: Core (No specific database)
• Environment: PostgreSQL 8.3.1
• Assignee: Thomas Dudziak
• Reporter: Cordeo
• Created: 03/Jun/08 12:51
• Updated: 05/Nov/08 06:33

Description

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.

Issue Links

• relates to: DDLUTILS-125 Add support for "START WITH"