QUOTE(nick2price @ 10 Oct, 2008 - 02:10 PM)
My classes are completely in a three tiered structure, so i have data, busines and logic seperated, so my gui only contains gui code and any actions are referenced from its appropiate methods class.
Excellent!
QUOTE
For my JDBC quiries, i'm not sure what you mean but transactions, but i rollback the connection on any errors and i commit the connection after every query. Does this mean my program would handle concurrent client users as it stands? Or does it need additional code?
Well transactions are basically SQL constructs to ensure consistency, basically what you say is:
SQL
BEGIN TRANSACTION
UPDATE statements;
SELECT statements;
UPDATE statements;
COMMIT/ROLLBACK;
Any changes within the transaction are invisible to the rest of the database until they're committed, but the changes will be visible within the transaction. The only extra step you need to make to properly use transactions is to explicitly begin them.
In many cases this should be sufficient for ensuring consistency between clients, but just to be sure, take a look at
transaction isolation. Another thing to keep in mind is that if your database is mapped to model objects, those objects may become out of date.
This post has been edited by JeroenFM: 11 Oct, 2008 - 02:58 AM
10 Oct, 2008 - 12:39 PM
| 