Multiple databases Application with Mobility

Question

Assuming a context of the "key value" strategy, and an application using multiple databases where each database has distinct tables and their translatable attributes, each of these databases will have a migration creating tables with identical names.

I forsee conflicts when reading and writing, as the classes Mobility::ActiveRecord::StringTranslation Mobility::ActiveRecord::TextTranslation might be invoked but not connect to the proper database.

Is this a valid concern? and
What would then be a valid strategy for Mobility in this context?