this is all we do to setup the database link CREATE PUBLIC DATABASE LINK foreign_DB1 CONNECT TO foreignOwner IDENTIFIED BY foreignOwner USING 'foreign_DB!';
CREATE PUBLIC SYNONYM foreign_table1 FOR foreign_table1@foreignOwner; thanks for looking into this On Sunday, July 19, 2020 at 11:47:24 PM UTC-4, Jeremy Evans wrote: > > On Sunday, July 19, 2020 at 1:02:09 PM UTC-7, Charles Monteiro wrote: >> >> so we have foreign table which we can certainly query with jdbc but using >> Sequel's "schema" api fails, that returns a message stating that the table >> can't be found. >> We have setup the public synonym for the table and that's is what we are >> passing to the schema api. >> >> So I guess the question is is there anything in particular that needs to >> be done at the database level to make the database linked table name >> "resolvable" by Sequel ? >> I have also tried to pass what I think may be the qualified path to the >> i.e. "external_database.target_table" but did not work either. >> >> Any insights are appreciated , thanks >> > > If you can give an example of how to get the linked table schema using > SQL, it's possible I'll be able to add support to Sequel for this. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/3cbc492f-f783-4f70-8a0e-88a4de7229a9o%40googlegroups.com.
