Error when attempting to join relations across different databases about rom-sql

[flash-gordon]

Different gateways use different connections by design, and joining across different connections is not possible. However, there's no check in the code ensuring you don't do that. The results you see are quite random. I'm not sure if rom-sql can generate identifiers that include the database name, it probably can't. We have a similar problem in PG where explicit schemas in resulting SQL are not supported. Once that support is added we can think of a convenient API for MySQL as well

[MasanoriOnishi]

@flash-gordon Thank you for your kind comment.
If the #405 is merged, the problem will be solved...??

That's because I think the pr will make it possible.
Sequel.qualify("legacy","other_users")

p default_relation.join(Sequel.qualify("legacy", "other_users"), container.gateways[:default][:users][:id] => container.gateways[:legacy][:other_users][:default_id])

[flash-gordon]

Hard to tell, I wouldn't hope for it TBH. Problem is we don't have a proper abstraction for schemas (PG, Oracle)/databases (MySQL) in rom-sql itself, making all our attempts to bypass that leaky. That said, having a method (or even a patch) in one's codebase is not a big deal, IMO.
Another approach: DB synonyms may work in MySQL, take a look https://blog.mclaughlinsoftware.com/2013/11/24/mysql-synonym/