Thanks for your help. But still, do you think there could be a way to
alter the dblink_current_query() function so that it could return the
right query? Or should I try to build the query in a function and send
it through dblink instead of dblink_current_query()?
I've also been told that oracle
Tom Lane wrote:
Joao Afonso <[EMAIL PROTECTED]> writes:
So (finally), my question is why does this happen? Using instead on
the users_util insert rule shouldn't discard the original query and
rewrite it according to the specified on the rule?? Is this a problem
of dblink?
I hadn't noticed th
Joao Afonso <[EMAIL PROTECTED]> writes:
> So (finally), my question is why does this happen? Using instead on
> the users_util insert rule shouldn't discard the original query and
> rewrite it according to the specified on the rule?? Is this a problem
> of dblink?
I hadn't noticed the dblink_cur
Hi!
I'm using dblink with some DBs and i'm having a few problems, more
precisely with the dblink_current_query() function.
First I create the following views on a DB:
- create or replace view users as
select *
from dblink('hostaddr=127.0.0.1 dbname=teste user=postgres
password=postgres','se
