Hello users,
A while back I had posted about running different versions on a desktop to see
if it caused conflicts, created problems and so on.
The versions in question are 4.0.1 and 4.1.3. For a lengthy time, I had used
4.0.1 in my dev. environment and 4.1.3 on our production server, both of these
servers in question being Win2K.
Several of you replied back and said there should be no problem, and while on
version wouldn't do DBCP and the other would allow for it, there seems like
little difference.
One thing that previously worked in both environments and now seems to not work
ok is the structure of a Prepared Statement.
I'll create one like I always have, and now Oracle seems to see the semicolon
ending the SQL statement as an illegal character, whereas before it did not.
I'm not saying or implying this is a Tomcat deal, but I wonder why it would
work before and now suddenly would not.
Basic prepared statement might look like this:
String prepquer = "UPDATE users_dev SET user_name = ?, USER_PASS = ?,
USER_TIMSTMP = SYSDATE, USER_DBFLGAG = 0" +
" WHERE user_name = ?;";
PreparedStatement preps = connection.prepareStatement(prepquer);
The console now gives me this error,
java.sql.SQLException: ORA-00911: invalid character.
I say now, this behavior actually started coincidentally after I started using
4.1.3 in my dev. environment.
If anyone can shed light on this here, feel free. Maybe I should address it in
the Oracle forum, which I'll probably go ahead and do.
But if it's concretely not Tomcat, let me know that, too.
Thanks!
