yeah, Chris, at one point I did update the Oracle driver, and looking back, I believe that was the difference.
In most cases I'm running stored procedures anyway, but occasionally I may be running a small prepared statement. -----Original Message----- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 20, 2007 3:12 PM To: Tomcat Users List Subject: Re: 4.x series difference -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Barry, Propes, Barry L [GCG-NAOT] wrote: > 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. Have you upgraded your Oracle driver in the process? I have never put semi-colons in any of my prepared statements, since it's not actually part of the statement. Usually, the semi-colon is the statement delimiter for a command-line interface. Since only a single statement can be executed (right?) through a prepared statement, I would just remove the semi-colon altogether, since it's not necessary (or even correct?). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGAEAj9CaO5/Lv0PARAsjsAJ0YEvRWS5yP2ZeXu4WQFAq1edXhBQCeMtJc 6kXOQpEcyg1XTHiymsgkS6s= =qSr+ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
