Plinio Conti wrote:
Yes, I think I will do it with an additional table on the db server, for the moment (I have no time to implement parsing etc...)
The problem is, like you stated, to mantain that table up to date with changes in system tables. The best solution would be a trigger for this, but we haven't them at the moment in MySQL.
Since any other solution will expose the client app to the possibility it has invalid information, I will have to handle access denied etc... but this is the less.
I will have to pray system administrators to do user management exclusivly through a special application provided by me, which will keep the *table* updated.
If administrators will use MySQL to store other databases than mine, my solution will be quite poor.
There's a middle road. Since you're writing a program to maintain your additional table anyway, you could (should?) write a cron job to make sure it stays in sync. That way, instead of relying on humans (the system administrators) to do the right thing, you automatically fix it for them when they don't. Have it run once a day, every hour, every 10 minutes, ... whatever frequency seems the best balance for your app. In fact, if you're willing to live with the lag, and don't trust your SAs, you could skip the user management app and stick with just the cron job.
Michael
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
