Would like some general advice on a multi-user application
Posted: Thu 24 Aug 2006 20:34
Hello,
I am developing a multi-user application and am just curious as to a few things.
1) When a record is added or updated....what is the best way to let the other running apps know that this data was updated? Have the other apps just do a refresh every so often? Or perhaps send a message to the other apps to refresh that query / table? Doing it this way would definitely increase the complexity of the program.
Or maybe have another table that has a records that point to all the other tables and timestamp it...and have all the other apps look every so often and see if any tables were updated?
Or is there some other way?
2) What is a InnoDB table? Should I be using this type for a small to midsize database?
3) Should I just lock a record or lock the whole table when a user makes a change, adds or deletes a record?
4) Are there any other pitfalls that I can avoid before I start in on this?
I am developing a multi-user application and am just curious as to a few things.
1) When a record is added or updated....what is the best way to let the other running apps know that this data was updated? Have the other apps just do a refresh every so often? Or perhaps send a message to the other apps to refresh that query / table? Doing it this way would definitely increase the complexity of the program.
Or maybe have another table that has a records that point to all the other tables and timestamp it...and have all the other apps look every so often and see if any tables were updated?
Or is there some other way?
2) What is a InnoDB table? Should I be using this type for a small to midsize database?
3) Should I just lock a record or lock the whole table when a user makes a change, adds or deletes a record?
4) Are there any other pitfalls that I can avoid before I start in on this?