ok, strangely now after removing that semicolon it works as it did/should. Might have been an old driver I was using before that allowed that I suppose.
-----Original Message----- From: Edmund Urbani [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 20, 2007 1:53 PM To: Tomcat Users List Subject: Re: 4.x series difference Propes, Barry L [GCG-NAOT] wrote: > 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! > Not sure whether this has anything to do with your problem, but I think it's odd that your SQL statement has a trailing semicolon. I never use semicolons with JDBC. So I thought maybe that's the "invalid character". ... not that this would explain why you get this error now and not earlier... Cheers, Edmund --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
