Move document compositing out of file compositing loop
Add unit test (that fails) that outlines correct behavior for diffing schemas
Use magic format_ class names in sql99_diff_tables instead of hardcoded sql99_ classes
Consider a mysql5 table to be renamed if it moved schemas, consider a table to be moved if it has an oldSchemaName
Add more cases to schema diff unit test
Use mysql5_diff::update_structure instead of the simulated diff from CompleteTableDiffTest
Throw if trying to use more than one schema without schema name prefixing
Add utility function to find the old version of a table, accounting for oldnames
Correctly handle tables moving between schemas in all combinations of using oldSchemaName and schema prefix mode
Drop the rest of the schema objects when dropping a schema, add matching test cases
Fix to_array case where $thing is an empty SimpleXMLElement
Fix case where dbsteward::$old_database is null
Update TableDiffSQLTest to understand schema name prefixing
Fix dbx::to_array for certain cases, simplify mysql5_type::get_enum_type_declaration
Don't prefix prefix the sequences table name. We will probably want to change this behavior at some point, but for now it's fine.
Bring unit tests up to date and passing
Merge branch 'dev-mysql5-schemas'

This fixes issues with diffing mysql5 schemas. Namely, due to too much
ambiguity, you can no long use multiple schemas without using the
--useschemaprefix flag. Additionally, DBSteward now handles moving
tables between schemas as renames if an oldSchemaName attribute is
present on the table. Finally, DBSteward now drops all of a schema's
objects if the entire schema was dropped. Prior to this, it assumed
that deleting a "schema" implicitly dropped all objects in it, like
pgsql8 does.