Home » SQL & PL/SQL » SQL & PL/SQL » executeQuery vs. executeUpdate on a resultset
executeQuery vs. executeUpdate on a resultset [message #202434] Thu, 09 November 2006 14:37 Go to next message
Messages: 13
Registered: October 2005
Junior Member
it is known that on a given resultset, executeQuery is only to use for executing SELECTs and executeUpdate for INSERTs, UPDATEs and DELETEs, but what could be the problem if for example I have and INSERT and execute it with executeQuery?
Re: executeQuery vs. executeUpdate on a resultset [message #202436 is a reply to message #202434] Thu, 09 November 2006 15:09 Go to previous message
Messages: 24958
Registered: January 2009
Location: SoCal
Senior Member
This appears to be a JAVA specific question & has little to do with Oracle; since JAVA is a database independent language.
Previous Topic: problem in creating user-defined aggregate function.
Next Topic: Global temp table Vs Nested table.
Goto Forum:

Current Time: Sun Oct 23 19:17:24 CDT 2016

Total time taken to generate the page: 0.09082 seconds