Re: Bug with Multiple Result Sets?

Hi. An execute() call may cause the DBMS to return any number
of update counts and/or result sets in any order. The return from
execute() says whether the first thing returned is a result set.
GetMoreResults() moves the processing to the next output to
process, and returns true if the next output is a result set.
The same SQL may return a different series of outputs for
different DBMSes, based on procedure definitions, triggers etc,
however, if one driver returns more valid info than another,
that may be a driver bug.
Joe Weinstein at BEA Systems

.

Relevant Pages

  • A big favor to ask of any C+OCI programmer to show a DBMS bug...
    ... to prove to Oracle DBMS support that there is a DBMS ... execute "TRUNCATE TABLE MYTABLE". ... Then the user will verify from SQL-plus ...
    (comp.databases.oracle.server)
  • Re: "no answer from RMCMD" error
    ... Certain functions in VDBA cannot be executed directly on the DBMS, ... instead a request to execute the function is loaded into a queue, ... The server-side process is the Remote Command Server, ... "ingstart" is being executed by a non-ingres user, ...
    (comp.databases.ingres)
Loading