Hi Marcello.
It's my understanding that only SQL statements that return a value of some kind
will return the data you expect. To do what you are trying to do, you would
need a persistent connection, and then a way to monitor that connection for any
data coming back over the socket. I suppose t
On 28/apr/2010, at 11.12, Sarah Reichelt wrote:
> If you check "the result" after your revExecuteSQL statement, it
> should contain the data you need.
Hi Sarah,
thank you for your answer.
"the result" of revExecuteSql doesn't seem to contains the information the sql
engine answers and I need t
On Tue, Apr 27, 2010 at 6:36 PM, Marcello Bertoli wrote:
> Hi all,
>
> I have a question about runrev database commands. Is there a way to get the
> result of a sql statement that doesn't retrieve data (is not a select)? For
> example:
>
> In a postgresql scenario I need to execute the statement
Hi all,
I have a question about runrev database commands. Is there a way to get the
result of a sql statement that doesn't retrieve data (is not a select)? For
example:
In a postgresql scenario I need to execute the statement:
"listen foo"
and I need to retrieve the result.
It seems that the