Hi Mike,
I was migrating a fairly significant database from MS SQL to PostgreSQL and when it was all finished, it undid itself.
I didn't say anything that I could use to figure out why.
Is there any way to tell WHAT was invalid, or what it was trying to do at that point (apparently after finishing).
Yes, please set the log level to SQL & Errors under Tools -> Options, and rerun the migration to create an SQL log. Unfortunately this will slow down things somewhat, so if you can do it with an exact copy of the table, just with fewer rows it would probably be less painful.
Maybe a feature that would commit after the table is built, and after each index is built. At least this might have saved me a day's work and the attempt to find some other way to move my database to PostgreSQL.
You probably saw the per-table commit option. Most people don't even use that, never mind a per-object commit :-(
Regards, Dave.