>Gunnar,

>One thing I know for certain is that you want to code the trigger to be as quick as possible. Trigger running for hours is not an acceptable solution.


I tend to agree - just didn't know another way.


>Also, you don't want to mix UI with the database logic, so the details about AJAX, etc., are not relevant here at this point.

Not sure if I understand you correctly. The user interface (java) would start a php program (bussines logic) which checks the tables via database logic, so I think that would be nicly seperated. However, I don't know if the php will continue to run even if the user disconnect from the internet. I would think that the php will continue to run (on the server) untill its finished, but I am not sure.


>What is the best solution from the database perspective for such problems - I don't know - may be more people can jump into this thread (especially ones familiar with MySQL specifics).

I would appreciate all the comments and recomendations!

Thank you for your help!