XML SQL Utility problem

Question

Hi,
I'm trying to use the XML SQL Utility against a 8.0.5 database.
I coded a basic query against the SCOTT.EMP table.
I've instantiated an OracleXMLQuery object using both types of
constructors (i.e. Connection + ResultSet or query String). In
both cases the resulting XML String contains:
<?xml version="1.0"?>
<ERROR>Closed Resultset</ERROR>
I know that my Connection and ResultSet objects are valid because
I examined the ResultSet contents using standard JDBC getXXX
methods for the same Connection and query. I am establishing my
Connection using the thin driver. Is this the problem? Can you
also elaborate on the Oracle specific requirements for this API?
For example, will the API work for Connection and ResultSet
objects against non-Oracle databases? Thanks.
Fred
null

Answer 1

Hi Fred,
The closed ResultSet problem would occur when u are trying to
re-use the same object,
e.g.
OracleXMLQuery oxq = new OracleXMLQuery(conn,resultsetobject);
// get the string..
String xmlString = oxq.getXMLString();
By default OracleXMLQuery closes the ResultSet after
completion. so if u use.
xmlString = oxq.getXMLString();
again, you will get this error.
To overcome this there is a call called keepCursorAlive() which
takes in a boolean value. So call that function on oxq before
getting the first string and everything will be all right.
Currently we also close the resultSet given by the user. This
is a bug (we should only close our internal resultset) and we
will fix it in the next drop. Also we will make this error
message much more legible!
Regarding working against other databases, we use Oracle
specific stuff currently in case of object features such as
ADTs, REFs and collections and LOBs. For regular relational data
such as number, varchar etc.., we don't do anything special.
So for plain relational data this should work against
ResultSet and Connection objects created from other databases.
But to be honest, we haven't tested that out. So if you do
indeed run into any problems with other databases, please let us
know and we will try to fix it.
Thx
Murali
Fred Criscuolo (guest) wrote:
: Hi,
: I'm trying to use the XML SQL Utility against a 8.0.5 database.
: I coded a basic query against the SCOTT.EMP table.
: I've instantiated an OracleXMLQuery object using both types of
: constructors (i.e. Connection + ResultSet or query String).
In
: both cases the resulting XML String contains:
: <?xml version="1.0"?>
: <ERROR>Closed Resultset</ERROR>
: I know that my Connection and ResultSet objects are valid
because
: I examined the ResultSet contents using standard JDBC getXXX
: methods for the same Connection and query. I am establishing
my
: Connection using the thin driver. Is this the problem? Can
you
: also elaborate on the Oracle specific requirements for this
API?
: For example, will the API work for Connection and ResultSet
: objects against non-Oracle databases? Thanks.
: Fred
null