Will Bryant

Sorry for the delay. I think I've finally figured out why this would happen. The only way I know of to create this problem is if the two databases sort...

I had a bit of a go at making a PG12 collation that would match MySQL's, but I haven't found it. Creating a case-insensitive collation is easy enough but they...

What KS version, PG version, and OS?

When I run the above statements in psql and then look at the output, only the source has a primary key; the target doesn't. So the two schemas don't match,...

Are you seeing different behavior to the above with Google Cloud SQL?

Wait, I get this for the first example - note that my output *does* have a PRIMARY KEY, whereas yours doesn't. My source table doesn't have the other constraints (because...

Added the other tables (just dummy tables with the id column) so that I can create the other constraints. It still works OK locally (pg 13.3). I guess I'll try...

That works fine for me too, so I can't reproduce the issue @RostislavKonstantinov :|. Created these two instances: Pasted the above SQL into the first, then ran: ``` $ ./ks...

Ah! That's very interesting. I don't know why that happens. Maybe it does not have enough permissions to read some of the schema information tables, so it misses some schema...

Unfortunately KS doesn't know about charsets and collation orders yet. It's actually pretty easy to add but it would be nonportable between databases which is awkward. Because most people use...