Jeremy: thanks
Full disclosure which may be helpful, we have a mirror database of Oracle in Postgres, pg has a similar concept i.e. foreign data wrappers , we don't have a problem with the schema api when used within PG, it may be that PG knows how to resolve the name or somehow was set up to do so by default. If Oracle requires extra steps I don't know , frankly not my area of expertise On Sunday, July 19, 2020 at 4:02:09 PM UTC-4, 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 > -- 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/9f7a13a5-3185-42f6-95c3-c68ca80b24fdo%40googlegroups.com.
