reorder some columns in the test schema's secondtbl to make it possible to test out a forthcoming scenario
give more helpful output if tests fail due to an EOFError while reading a command
improve a test so it doesn't mess with the PK order
extract the database-specific key clearer glue out of the database client classes using a trait class and specialization
all clients will quote identifiers, don't need to be conditional
drop tables, columns, and keys if necessary to make the target schema match
implement adding and replacing keys to match the source schema
automatically add missing tables
recreate the table if the primary key doesn't match
update the list of key columns when dropping columns, to match what the database servers do, so the next stage will have an accurate list to work from
wip on adding/dropping/replacing columns