Re: ResultSet.updateString against DB2 giving "Column not updatable"
- From: adamcrume@xxxxxxxxx
- Date: 29 Jun 2006 08:39:44 -0700
If that's what's happening, the driver's not only being silent but
devious. I tested the result set after it was created:
System.out.println("Type correct: "+
(rs.getType()==ResultSet.TYPE_FORWARD_ONLY));
System.out.println("Concurrency correct: "+
(rs.getConcurrency()==ResultSet.CONCUR_UPDATABLE));
These printed out true and true.
I'm curious how you arrived at your conclusion. Are you aware of a
DB2-specific issue? If so, could you reference any documentation?
Joe Weinstein wrote:
Hi. There's nothing wrong with your JDBC. It seems the
driver is silently downgrading your ResultSet to a
non updateable one. Check the driver documents about this.
Joe Weinstein at BEA Systems
.
- Follow-Ups:
- Re: ResultSet.updateString against DB2 giving "Column not updatable"
- From: joeNOSPAM@xxxxxxx
- Re: ResultSet.updateString against DB2 giving "Column not updatable"
- References:
- ResultSet.updateString against DB2 giving "Column not updatable"
- From: adamcrume
- Re: ResultSet.updateString against DB2 giving "Column not updatable"
- From: Joe Weinstein
- ResultSet.updateString against DB2 giving "Column not updatable"
- Prev by Date: Re: ResultSet.updateString against DB2 giving "Column not updatable"
- Next by Date: Re: ResultSet.updateString against DB2 giving "Column not updatable"
- Previous by thread: Re: ResultSet.updateString against DB2 giving "Column not updatable"
- Next by thread: Re: ResultSet.updateString against DB2 giving "Column not updatable"
- Index(es):