I'm working on a Java program that inserts and updates data in a DB2 database. For performance reasons, I'm trying to use prepared statements to queue the data and submit the changes all at once. However, I think I've run into a conceptual block - a number of decisions the program makes are based on data that is both already in the database and queued up in the prepared statements. It seems that standard SELECTs can only see the data that is committed in the database and not the data in the queue.
Am I "doomed" to be forced to commit my changes as I make them in order for the SELECTs to see them, or is there a way that a SELECT query (or something like it) can account for both the data already in the database and the data to be executed in the prepared statements?
Thanks,
David