No updateable ResultSet

Hi,
I'm trying to do an update with the ResultSet, but I always get an exception
that I can't do an update on a read-only ResultSet. I set the
ResultSet.CONCUR_UPDATABLE but it is not working.
Here is the code:
//-------------------------------------------PreparedStatement stmt = conn.prepareStatement(SELECT_CD,
ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
// debug message
cat.debug("Statement: " + stmt.getResultSetConcurrency());
// do some filling of the prepared statement
ResultSet rs = stmt.executeQuery();
// debug messages
cat.debug("CONCUR_UPDATABLE: " + rs.CONCUR_UPDATABLE);
cat.debug("CONCUR_READ_ONLY: " + rs.CONCUR_READ_ONLY);
cat.debug("ResultSet: " + rs.getConcurrency());
// update
if(rs.next())
// we have an entry
rs.updateString(4, srcSystemInstance());
rs.updateString(5, srcSystemType());
rs.updateRow();
The output of the debug messages:
Statement: 1008
CONCUR_UPDATABLE: 1008
CONCUR_READ_ONLY: 1007
ResultSet: 1007
Even the statement is updateable, the ResultSet is still read-only.
I'm using JDK1.3 under Window2000 and connecting to an Oracle 8.1.6 database
with the OCI driver. (Oracle driver version 8.1.7.0.0).
Any ideas what is wrong?
Best Regards
Juergen
null

When I tried it I did something like where dbConn is a working connection to Oracle (I can fetch data just fine). I tried a regular SELECT *, SELECT * with a WHERE clause, and using FOR UPDATE. All combinations fail
and the dbConn is not read only, the statement is CONCUR_UPDATABLE, but the resultset is always read only.
stmtw=
dbConn.createStatement(
ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATABLE);
System.out.println("STMTW Concurrency is "+stmtw.getResultSetConcurrency()+" and should be "+ResultSet.CONCUR_UPDATABLE +" and not "+ResultSet.CONCUR_READ_ONLY);
rsw=
stmtw.executeQuery(
"SELECT * FROM WTHR FOR UPDATE");
System.out.println("DB READONLY :"+dbConn.isReadOnly());
System.out.println("RSW Concurrency is "+rsw.getConcurrency()+" and should be "+ResultSet.CONCUR_UPDATABLE +" and not "+ResultSet.CONCUR_READ_ONLY);
null

Similar Messages

Scrollable/Updateable ResultSet objects

I am trying to create an instance of a scrollable/updateable ResultSet object with the following code:
Statement stmt = con.createStatement(
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_UPDATABLE);
ResultSet rs = stmt.executeQuery("SELECT * FROM sch.a");
The Connection object has been made successfully but am getting an AbstractMethodError Exception at line 1.
Can anyone please help me out here.
Thanks
I am using JDK 1.3.1 and JDBC 2.0

I use this and works fine for me....let me know how it goes...
ResultSet resultSetMultCond = null;
Statement getMultPartCond = null;
String sqlMultCond = null;
sqlMultCond = "SELECT #PART,#CONDS,COUNT(*) AS MCOUNT FROM MYLIB WHERE #PART = 'A123' GROUP BY #PART,#CONDS ORDER BY #PART";
getMultPartCond = conn.createStatement(java.sql.ResultSet.TYPE_SCROLL_SENSITIVE,java.sql.ResultSet.CONCUR_UPDATABLE);
resultSetMultCond = getMultPartCond.executeQuery(sqlMultCond);

Problem with Updateable ResultSet

Hi,
I'm having a problem updating an updateable resultset. When I query the database using anything other than the LIKE clause, I can update the resultset just fine. As soon as I add the LIKE clause to my select query and then try to update one of the records in the resultset I get an "Error in row". The database I am using is MS Access (yes I know, not a good choice), and I am using the driver that comes built into Java. I am also running JDK 1.5_06.
I've looked to see if maybe this is a known bug, but haven't found anything related to this. Has anyone else seen this same problem? Or know of a way to get around it?
Thank you in advance.

I'm confused then... Why would I be able to update
the resultset when I select that resultset not using
the LIKE clause, but when I use the LIKE clause to
get the resultset and then try to update it in some
way, I get an error. Because the database isn't giving you an updatable cursor if you use a like apparently. It just isn't. Don't know why.
Obviously the resultset is
updateable, Obviously not.
and I have selected the right cursor type
for each parameter (TYPE_SCROLL_INSENSITIVE and
CONCUR_UPDATABALE). I am sure you are but what you ask for is not always what you get.
I understand that it is not
required for the database and/or driver to fulfill my
wishes, but it seems odd Yes it does seem a bit odd but that doesn't make it less true. To be frank with you I can't remember the last time I used an updatable result set.
It's one of these things that seem all nifty at first but it's all very quirky and resource intensive and in almost all cases was better handled by an INSERT, UPDATE or DELETE statement in the first place.
that it I am able to update
the resultset when I have not used the LIKE clause to
create it, but am unable to update it when having
created it using the LIKE clause. :shrug: Because. I couldn't tell you why it does it this way. I am sure it has something to do with how it builds the cursor... generally in MS database stuff there are dynamic and static (or fixed I can't remember the names) "keysets" for a given result set. I am mangling the terminolgy here but it doesn't really matter... the point is with MS databases the way you search combined with any clauses combined with what fields you select all effect the ending cursor types you can have. This is true for most databases really... and to make a long story short I guess that a LIKE is just making the backing keyset or whatever non updatable.
I'll try your tip
of listing all of the columns instead of using * to
see if that makes a difference.It might but don't get your hopes up.
This is a general tip you can use to try and get an updatable cursor but honestly in your case I am not sure it will help. It seems to me that you are going to have to not use LIKE.
Which means you can either give up the updatable cursor OR the like. If you have to have an updatable cursor AND the LIKE then you are going to have to do this in two steps.
Query 1 - Select the keys by LIKE
Query 2 - Select updatable cursor using the keys from query 1
But that seems terribly painful.

Need to obtain updateable ResultSet via call to PL/SQL function

I'm using JDBC and the Oracle JDBC driver to call a PL/SQL function that returns a SYS_REFCURSOR. I do this via a CallableStatement object and then cast the output parameter to a ResultSet object. However, I want this ResultSet object I end up with to be updateable. The following code throws an exception stating "Invalid operation for read only resultset: updateString ":
cstmt2 = con.prepareCall("{? = call get_upload_entry_for_update(?)}",
                         ResultSet.TYPE_FORWARD_ONLY,
                         ResultSet.CONCUR_UPDATABLE);
cstmt2.registerOutParameter(1, OracleTypes.CURSOR);
cstmt2.setInt(2, newUploadId);
cstmt2.execute();
rs = (ResultSet) cstmt2.getObject(1);
rs.next();
rs.updateString("UPLOAD_FILENAME", fileName);
// . . .So even though, I create the CallableStatement such that ResultSets should be updateable, it's not allowing me to do any updates. Also, in case you're wondering, inside the PL/SQL function, the query on which the cursor is based is a select statement which does specify "for update" at the end.
I can get it to work as follows using a Statement object that executes the SELECT statement directly instead of a CallableStatement that executes a PL/SQL function:
Statement stmt = con.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE);
rs = stmt.executeQuery("select UPLOAD_FILENAME, UPLOAD_FILE from rf_upload where upload_id = "+newUploadId+" for update");
rs.next();
rs.updateString("UPLOAD_FILENAME", fileName);
//. . . Although this works, the project I'm working has a goal to encapsulate all SQL into Functions and Stored Procedures so I'd like to get it working that way instead.
So the bottom-line question is: Using the Oracle JDBC driver, how can I call a PL/SQL function in such a way that I can obtain an updateable ResultSet object?
Thanks for any suggestions. I'd be happy to clarify anything that's unclear.

Hmmm...
I'm still scratching my head about this one, just not sure it's doable, but I'll point out something, maybe it will give you a clue...
In your code, you have:
cstmt2 = con.prepareCall("{? = call get_upload_entry_for_update(?)}",
                         ResultSet.TYPE_FORWARD_ONLY,
                         ResultSet.CONCUR_UPDATABLE);I don't think the ResultSet parameters do anything towards your goal of getting an updatable result set via the returned cursor, those parameters affect the result set produced if you were to call:
ResultSet rs2 = cstmt2.executeQuery();and not the result set generated by:
rs = (ResultSet) cstmt2.getObject(1);Futhermore, while the "FOR UPDATE" is almost certainly something you want to do, it also doesn't affect the cursor (I think) but merely locks the affected rows in the DB.
You might try calling rs.getType() and rs.getConcurrency() on the ResultSet you get from getObject, though I suspect they'll merely confirm the bad news that the cursor your getting back isn't right...
You also might try the Oracle-specific getCursor call:
rs = ((OracleCallableStatement)cstmt2).getCursor (1)instead of getObject, though I don't think it will help...
I've been curious enough to dig around through most of my handy references and Oracle's docs and MetaLink and come up mostly empty, although almost 5 years ago Oracle Support said:
" Reference Cursors from a pl/sql stored procedure are not updateable in any language."

IBM DB2 with Updateable ResultSets

I'm working on a cross database application that uses updateable resultsets.
I've run it on mysql and postgres.
And using JTDS and DataDirect I've got SQL Server functionality working.
But now I'm trying to deploy it on DB2 using the UDB dirver. But it seems that it doesn't support Updatable ResultSets.
The driver I'm using came with the DB2 Personal Edition.
Is there another driver by IBM that supports updatable resultsets, or will I be forced inyo finding a thrid party driver for my work?

I believe I was using the type 4 one, but I got a SQL Exception simply saying "Driver not Capable" when I ran it.
The DataDirect one should work, but it is also responsible for connection hijacking.
What that is that once you register the DB2 Driver, and you use DriverManager to get a connection, it assumes that ALL calls to DriverManager.getConnection() are for DB2 connections, even though I use Postgres connections as well. When I try to get a postgres connection, the DB2 driver throws an exception saying that it can't connect to the datasource!

How to create updateable resultset using sql with "order by"

Dear all,
I'm using the Derby database to hold a table of stock prices. After the table is populated, I want to do some calculations and store the result in a column.
I get the resultset using the following code
Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE); ResultSet rs = stmt.executeQuery(select history_id, value, days from history where ticker = '" + ticker + "' order by value_date"); {code} When I then try to update the "days" field, I get an SQLException telling me that the resultset is not updatable. However, if I remove the "order by" clause, I am able to update the data, but then my algorithm does not work as I need to traverse the data in a specific order. The quesion is: how do I create an updatable resultset using a sql-statement with an order by clause? Kind regards Karl Martin Lund

jschell wrote:
Seems rather obvious to me that the exception specifically tells you that you can't do that.OP: I would guess it's because ORDER BY forces the database to read all the result rows into a temporary area, sort them, and then return them from this temporary area, as opposed to streaming the results. The extra step probably makes updateable result sets more difficult (or maybe not possible), so they opted not to do it.

How do I get an updateable ResultSet ?

Using Oracle 8.1.7 JDBC libs.
My code reads thus:
Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATABLE);
ResultSet rs = stmt.executeQuery("select * from my_table");
rs.moveToInsertRow();
.. yet I see this when I run it:
java.sql.SQLException: Invalid operation for read only resultset: moveToInsertRow
Any pointers?
Thanks,
- Michael

I'm partial to this series:
After Effects basics tutorials by Andrew Devis
The subject matter is very clearly-defined by topic.
And AE shouldn't up & quit on you... but you haven't breathed a word about your system or your AE version. Please share.

Probem with updateable resultset

i have large view in database , i want to update virtual columns in this view , i used resultset to update this virtual columns , but there are exception that resultset is readonly .
my question i want to update these virtual columns with resultset or cashrowset .
i want these to make some calculation in run time before run report .
Statement stmt = connection.createStatement(
ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
ResultSet resultSet = stmt.executeQuery("SELECT * FROM employeedata_view");
resultSet.first();
resultSet.updateString("col_string", "join");
resultSet.updateRow();

Does your database support update-able views? If not, there's no way it's going to work from Java.

Bug in Oracle UpdatableResultSet? (insert, updateString requires non-empty ResultSet?

As far as I can determine from the documentation and posts in other newsgroups
the following example should work to produce an updatable but "empty" ResultSet which can be used to insert rows.
But it doesn't work in a JDK 1.2.2 and JDK 1.3.0_01 application using Oracle 8i (8.1.7) thin JDBC
driver against an Oracle 8.1.5 database I get the following error
SQLException: java.sql.SQLException: Invalid argument(s) in call: setRowBufferAt
However, if I change it to so the target (ie insert) ResultSet is initialized to contain one or more
rows, it works just fine.
ResultSet rset2 = stmt2.executeQuery ( "select Context.* from Context where ContextCd = '0' " );
Is this a bug in Oracle's JDBC driver (more specifically, the UpdatableResultSet implimentation)?
Does an updatabable ResultSet have to return rows to be valid and useable for insert operations?
If it does, is there another way to create an updatable ResultSet that does not depend upon
"hard-coding" some known data value into the query?
try
// conn is a working, tested connection to an Oracle database via 8.1.7 thin JDBC driver.
// source statement
Statement stmt = conn.createStatement (
ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY );
System.out.println("source rset");
rset = stmt.executeQuery ( "select Context.* from Context" );
// target Statement
Statement stmt2 = conn.createStatement (
ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE );
ResultSet rset2 =
stmt2.executeQuery ( "select Context.* from Context where ContextCd = NULL" );
System.out.println(
"see if rset2 looks good even though empty (bcs primarykey = null)");
ResultSetMetaData rsmd2 = rset2.getMetaData();
int numColumns = rsmd2.getColumnCount();
for( int i = 0; i <= numColumns; i++ )
env.msg.println ( "(" + i + ") " + rsmd2.getColumnLabel(i) );
// test results showed the correct columns even though no row returned.
// quess we can use this trick to create an "empty" insert ResultSet.
System.out.println("interate through rset and insert using rset2");
if(rset.next())
System.out.println("move to insert row");
rset2.moveToInsertRow();
System.out.println("insert values");
rset2.updateString( "ContextCd", rset.getString("ContextCd") + "-test" );
rset2.updateString( "Descrip", "test" );
rset2.updateString( "Notes", "test" );
System.out.println("insert row into db (but not committed)");
rset2.insertRow();
catch( ... ) ...
Thanks
R.Parr
Temporal Arts

I have noticed the same problem, actually it doens't matter if there is no data in your resultset. If you have a result with data and suppose you were to analyze the data by moving through all of the rows, the cursor is now after the last row. If you call insertRow, the same exception is thrown. Kinda strange, I didn't get any response as to why this is happening and that was a few weeks ago. I hope someone responds, at this point I am just re-writing some of my code to not use updateable resultsets.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Randall Parr ([email protected]):
As far as I can determine from the documentation and posts in other newsgroups
the following example should work to produce an updatable but "empty" ResultSet which can be used to insert rows.
But it doesn't work in a JDK 1.2.2 and JDK 1.3.0_01 application using Oracle 8i (8.1.7) thin JDBC
driver against an Oracle 8.1.5 database I get the following error<HR></BLOCKQUOTE>
null

SQLException JDBC 2.0 ResultSet.CONCUR_UPDATABLE

Hi, i have a problem using JDBC 2.0, my cod is:
Statement c = conn.createStatement();
Statement =conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
ResultSet rest = n.executeQuery("select * from t_prueba");
rest.last();
rest.updateBlob("C", null);
rest.updateRow();
rest.close();c.close();conn.close();
at time to execute this code, i have this error:
java.sql.SQLException: Operaci�n no v�lida para el juego de resultados de s�lo lectura: updateBlob
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161)
     at oracle.jdbc.driver.BaseResultSet.updateBlob(BaseResultSet.java:482)
     at oracle.jdbc.driver.OracleResultSet.updateBlob(OracleResultSet.java:1230)
     at mypackage3.Conversor.leerImagenBase64(Conversor.java:51)
     at mypackage3.Conversor.main(Conversor.java:77)
why is this problem if i using ResultSet.CONCUR_UPDATABLE in my statement.
i 'm using jdeveloper 10.1.2 whith j2se 1.4.2_04
please anyone can help me please
tanks
alex

for updateable resultset your query must specify column names to select.

ResultSet updateRow() problem

The RDBMS I am working with is:
Apache Derby version = 10.1.2.1
I cannot seem to figure out why this ResultSet update is not working.
I create the ResultSet with the following:
Statement stmt = conn.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE, ResultSet.HOLD_CURSORS_OVER_COMMIT);The query that I execute to return the result set contains the primary key, FROM contains only one table, and the query contains no JOINS or UNIONS.
So then I call next()
Update all the columns that I am interested in updating, up to this point everything is fine, I can get the column that I updated out, and the values are the updated ones.
When I call updateRow(), I get: Invalid cursor state - no current row
But there is a current row, I am updating columns in it and those updates are taking place.
Any help is appreciated.
Thanks

yes, it returns true.
and it is the row that I am interested in. If
immediately after the next() I get one of the
columns, it is the correct value, then I set it using
updateXXX, then get it out again it is the updated
value. All as I would expect it to work.
But on the call to updateRow() - Invalid cursor state
- no current row.Then I would suspect that the database driver you're using doesn't support updateable resultsets (?)
You do realize that not all databases support that, right?
Although it would seem that you should get a different error message in that case, hence the (?) above.

Passing a resultset to a method

Hi all,
I want to pass a resultset object that is scrollable and updateable to a method. THe problem is that, the resultset object in the other method is not scrollable or updateable anymore.
Eg.
Statement stat = null;
ResultSet rs = null;
stat = connection.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATEABLE);
rs = executeQuery("SELECT * from table");
rs.absolute(5); // when i use this, it works fine here, but it won't if i pass rs to another method
method2(rs);
// end of this method
method2(ResultSet rs) {
absolute(5); //this is where i am told that ResultSet is readonly and not updateable
OFFCOURSE, ignore the syntax errors and stuff. I would greatly appreciate your help. I really need to figure this out otherwise i would have to rewirte a huge part of my code. Thank you very much

warnerja is only partially right, it is true that database driver sometimes doesn't support updateable resultset, but my problem was solved by following this link
http://www.oracle.com/forums/message.jsp?id=396810&pgm=otn&uid=1024413365365 (you have to register with oracle for that)
for anybody who can't access the above page, the solution is
instead of doing (SELECT * from abc), do (SELECT abc.* from abc)
that should solve your problem if its the same as mine.
HOWEVER, if i have multiple tables and if i do the following as above
SELECT abc.*, zzz.channel, zzz.channel2, xyz.field1
FROM abc, zzz, xyz
the resultset remains readonly, i dont' know why
ANY IDEAS???????

DataBase problem, when update ResultSet

Hi,
I use mysql drivers and the problem is:
i create a connection and then a statement with option CONCUR_UPDATABLE.
Calling stmt.getResulSetConcurrency(), the answer is CONCUR_UPDATABLE,
but if i execute a query, calling rs.getConcurrency() the answer is CONCUR_READ_ONLY!!
note: rs is the ResultSet return by the query.
In short: I can't update database throught ResultSet object!
And I have the permission to do!
Why?
thank you for answer.
Luca

Just because you request updateable resultsets doesn't mean the driver supports it. I don't know if MySQL supports it or not. If it does, then I'd have to guess that your particular query is done in such a way as to not be updateable. I believe if your query does a join, for example, it can't be updateable.

ResultSet updateRow ,insertRow ,deleteRow APIs on table with no PRIMARY KEY

Hi,
When I use ResultSet.insertRow , updateRow ,deleteRow API's on a table which contais no primary key column I find the following Exception ,
java.sql.SQLException: Operation invalid. No primary key for the table
at com.tandem.sqlmx.Messages.createSQLException(Messages.java:69)
at com.tandem.sqlmx.SQLMXResultSet.getKeyColumns(SQLMXResultSet.java:3501)
at com.tandem.sqlmx.SQLMXResultSet.prepareInsertStmt(SQLMXResultSet.java:3652)
at com.tandem.sqlmx.SQLMXResultSet.insertRow(SQLMXResultSet.java:2073)
at testdateupdate.main(testdateupdate.java:33)
It looks like the table needs to have a primary key column to update or insert or delete rows using the ResultSret APIs.
I use a proprietary JDBC driver. I find the Explanation for this behavior like this ,
JDBC allows update stmts on tables w/out a primary key defined if the stmt is issued by the application. For updateable ResultSets, a primary key restriction is required to avoid updating more rows than desired.I dont understand this explanation and also I dont find this behavior is some other JDBC drivers that I tried with.
Some one Please Clarify the same.
Thanks in Advance.
Thanks and Regards,
Jay

Hi,
in simple words, when a table does not have primary key you can send update and delete on it only by using a Statement object. When using ResultSet.updateRow or ResultSet.deleteRow the jdbc looks for the primary key on the metadata in order to send the correct where clause to the rdbms. I think that this could maybe work with Oracle DBMS, which has a unique id (ROWID) for each record.
Kiros

How can i get jdbc2.0 compatible driver for my oracle 8.1.5 client/server

Hi ,
I am looking for a driver that is jdbc2.0 compatible.Apaprently the oci and thin drvers that are shipped with oracle8.1.5 do no support scrollable and updateable resultsets. Can i download the oracle8.1.6 jdbc2.0 compatible drivers and use them with my oracle8.1.5 client/server. if so how do i install it?
Please let me know ASAP!!
It is relly frustrating to find a compatibler driver for the older versions since oracle does'nt provide them
poornima

Yes. For OCI driver, you will also have to have Oracle 8.1.6 client installed as well. http://technet.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#_1_

No updateable ResultSet

Similar Messages

Maybe you are looking for