mmatuson/SchemaSync — Issue #14: script analyses wrong databases
Author: pwhipp
Created: 2011-12-03 07:30:27+00:00
State: open

I initially tried
'schemasync mysql://root:xxx@localhost:3306/magento mysql://root:xxx@localhost:3306/another_db

The result was a slew of lines like this:
/usr/local/lib/python2.6/dist-packages/SchemaObject-0.5.3-py2.6.egg/schemaobject/connection.py:63: Warning: Triggers for table `alitoco_development`.`jos_users` have no creation context
cursor.execute(sql, values)
/usr/local/lib/python2.6/dist-packages/SchemaObject-0.5.3-py2.6.egg/schemaobject/connection.py:63: Warning: Triggers for table `empty_ptp`.`pp_activities` have no creation context
cursor.execute(sql, values)
...
These relate to other databases on localhost rather than those specified. I worked around the problem by switching from root to users that can only access the particular db of interest but this looks like a significant bug to me. Output was generated successfully when I used users that only had access to the single relevant db.