In addition, it doesn't check on both kinds of databases for

• DROP TABLE - that's why for the finder schema updates currently no errors are shown ;-)
• ALTER TABLE .. RENAME ... (renaming tables)

I plan to work on that.

Seems I‘ve made a mistake when checking this for @wilsonge : The schema checker for PostgreSQL DOES support column type changes, only the syntax is different to the (erroneous and meanwhile corrected) syntax in one of the recently corrected update SQL scripts.

But the other issues I‘ve mentioned in my previous comment are still valid.

@wilsonge Just change title and description of this one? Or close it because the other issues are expected behavior?

So the change column does work already (after the fixes we did on Saturday). It’s just deleting and renaming tables now?

@wilsonge Correct. But if we add support fopr "DROP TABLE" (tables are dropped, not deleted) we might have the same problem with Hannes' update SQL as we had whe we developed the utf8mb4 conversion and tried to drop and then add back an index with the same name, like Hannes does with a table in the update sql for the finder. It would need either make the schema checker more clever for this, or change the sql so the table is modified in the right way instead of drop and create again.

I suggest we close this issue.

@wilsonge For table rename I'm already working on a solution.