Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

limit on execSQLSelect statements

38 views
Skip to first unread message

pmattam

unread,
Nov 27, 2009, 5:59:17 AM11/27/09
to
Hi all,

I am using a script node to execute a few SQL statements on an Oracle
DB.

Qn1)
I understand that if you need to iterate the result set of a select
query, you have to use execSQLSelect followed by
getNextSQLSelectEntry. If I am using mutliple SQL Select statements
( and need to obtain the result value for each Select statements). in
the same script node, does the getNextSQLSelectEntry resultset get
reset each time? Do I need to do anything special for this?

Qn2) I wanted to execute an SQL query if the SELECt statement returns
"no rows found". Can this be achived using the getNextSQLSelectEntry?

Thanks in advance,
Preethy.

Eddie Hartman

unread,
Nov 30, 2009, 8:14:38 AM11/30/09
to
When you use the execSQLSelect, Preethy, you have to
first have a connection/session with your db. That you grab
from an initialized Connector. Each time you make the above
call you get a new result set. If you need more than one set
active, simply add another Connector and use its connection.

The getNextSQLSelectEntry function either returns the next
row from the currently active select, or null if no more are found.

An alternative is to use a Connector Loop with the JDBC Connector,
set the Loop to initialize the Connector each time and then map
the jdbcSelect param in the Parameter map tab.

Hope this helps!
-Eddie

0 new messages