JDBC Statement Bug with OracleLite 4.0.1.2?

Question

I have found what appears to be a bug. Has anyone else encountered this bug. I have the following code:
Statement stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery("select columnA,columnB from tableA");
while (rs.next())
System.out.println("ColumnA="+rs.getString("ColumnA"));
System.out.println("ColumnB="+rs.getString("ColumnB"));
rs.close();
rs = stmt.executeQuery("select column1, column2,column3 from Table1");
while (rs.next())
System.out.println("Column1="+rs.getString("Column1"));
System.out.println("Column2="+rs.getString("Column2"));
("Column3="+rs.getString("Column3"));
Column 3 is the problem. I get the
following Exception:
System.out.printlnjava.sql.SQLException: >>> [ODBC S1002] invalid column number
After researching it I found that you
cannot reuse a Statement object over and
over again. The reason is that the first
execution of a statement initializes the
number of columns to be returned and each
subsequent statement executed does not
reinitialize the column count. So in the
case above the column count is 2, and I
issue a query with 3 columns using the
same statement object, hence the bug.
I know the work around, just wanted to
know if this is a know bug.Any thoughts.
Mike H.

Answer 1

I've never heard of anything like this either. But I'm not sure I'm properly tracking what you say. You drop a PR file into the source well and it disappears? If you have a Finder window open and you drag it to the Batch window, you actually see the file deleted in the Finder window?
Or do you mean that the PR file doesn't get copied to the well?
Russ