preparedstatement addBatch
Dev Anand
Ranch Hand
Posts: 41
posted 5 years ago
Generally speaking, this is the most efficient way to do it, though various databases might differ a bit.
Just for an example - in Oracle, with JDBC driver older than 11g, this does not yield the most efficient mechanism; you'd need to use Oracle specific methods to achieve the best possible performance. With 11g JDBC driver, the standard JDBC batching achieves the topmost performance without need for any Oracle specific processing.
On the other way, you're not going to get significant savings on five or six executions. You should use the standard batching - no doubts about it, but that's probably all. On the other hand, if you'd be executing the command hundreds or thousands times, it might be a good idea to check with your specific JDBC driver/database documentation to find out whether a more efficient alternative exists. Or ask here again with the full database and JDBC driver specification; someone might be able to advice you in your particular situation.
Just for an example - in Oracle, with JDBC driver older than 11g, this does not yield the most efficient mechanism; you'd need to use Oracle specific methods to achieve the best possible performance. With 11g JDBC driver, the standard JDBC batching achieves the topmost performance without need for any Oracle specific processing.
On the other way, you're not going to get significant savings on five or six executions. You should use the standard batching - no doubts about it, but that's probably all. On the other hand, if you'd be executing the command hundreds or thousands times, it might be a good idea to check with your specific JDBC driver/database documentation to find out whether a more efficient alternative exists. Or ask here again with the full database and JDBC driver specification; someone might be able to advice you in your particular situation.
| It is sorta covered in the JavaRanch Style Guide. |