[EMPIREDB-284] Sequences left after dropping my PostGreSQL dataBase

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: empire-db-2.4.7
• Component/s: Core
• Assignee: Unassigned
• Reporter: Samir Hadzic
• Created: 18/Jan/19 15:42
• Updated: 04/May/20 11:00
• Resolved: 04/May/20 11:00

Description

This is the exact same issue of EMPIREDB-279.

In Postgresql we create a sequence when creating a Database :

 @Override
    protected void createDatabase(DBDatabase db, DBSQLScript script)
    {
        // Create all Sequences
        for (DBTable table : db.getTables())
        {
            for (DBColumn dbColumn : table.getColumns()) {
                DBTableColumn c = (DBTableColumn) dbColumn;
                if (c.getDataType() == DataType.AUTOINC) {
                    createSequence(db, c, script);
                }
            }
        }
        // default processing
        super.createDatabase(db, script);
    }

But there is nothing overriden for DDLscript when dropping the table in order to also drop the sequence.

Issue Links

• relates to: EMPIREDB-195 Review PostgreSQL driver's DDL generation for sequences
• relates to: EMPIREDB-279 Sequences left after dropping my Database. Can't create a new one.