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 has an auditing service that records every action the users make, including the queries issued. If pg has something like that I could use it instead. On 8/1/05, Tom Lane <[EMAIL PROTECTED]> 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 the dblink_current_query() function before, but now > that I see it, I consider it a pretty bad idea. It certainly will not > help you the way you are hoping, because what it returns is the text of > the interactive command the backend is currently working on --- which > could be indefinitely far removed from the operation your rule is firing > for. > > regards, tom lane > ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly