This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes JDBC and Relational Databases and the fly likes updateString fails with Java 1.3 and Oracle 9 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "updateString fails with Java 1.3 and Oracle 9" Watch "updateString fails with Java 1.3 and Oracle 9" New topic
Author

updateString fails with Java 1.3 and Oracle 9

Brant
Greenhorn

Joined: Jan 11, 2002
Posts: 1
I have the following configuration:
- Windows NT 2000 Server
- Tomcat 3.2.3
- Oracle 9
- JDBC Driver 9.0.1.1.0 (thin driver)
- classes12.zip in my jdbc\lib directory.
When I call the updateString ResultSet method the database receives garbled data (i.e. inverted question marks). I also get this same result after calling updateString and then calling getString.
However, when I call updateInt or other non-string update methods I do not have a problem.
I also don't have a problem calling updateString when using the same configuration but with Java 1.2.
Has anyone else run into this problem?
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: updateString fails with Java 1.3 and Oracle 9
 
It's not a secret anymore!