|Subject:||Re: Postgresql forcing query to run locally
|Date:||Tue, 21 Apr 2020 11:29:23 +1000
|From:||Tom Krieg <REMOVEtomkCAPITALS@sdassociates.com.au>
The joys of using PostgreSQL as a pseudo Paradox database. To run on the
server, everything required needs to be visible to Postgres. I keep
harping back on this point - trying to combine Paradox tables and
PostgreSQL tables in a datamodel or query is a bad idea.
On 21/04/2020 2:13 am, Mark Bannister wrote:
> I'm trying to run some queries with local tables against remote
> postgresql server.
> Something simple like:
> SELECT o.*
> FROM ':PRIV:__pncopy' o
> LEFT JOIN ':manager:partnum' p
> on p.id = o.id
> Where "manager" alias is postgresql server alias.
> When executesql is called and I define the database as "PRIV" then it
> runs locally, but it asks for a password for the "manager" alias.
> "Manager" has already been open.
> If I define the database as "manager" then it sends the query to the
> postgresql server which obviously doesn't know anything about files in
> the private directory. I tried making and postgresql alias defined to
> run locally only but that has no effect on this issue.
> Mark B