Richard Lynch wrote: > My current employer has designed a sort of CMS (except it has so many > site-specific hard-coded features that it's not a CMS at all) where things > happen such as: Your current employer? I didn't think CEOs had bosses... anywho ... > One idea I'm pondering goes like this: > > Create a session_action table, which has: Using this session_action table you are talking about is ok, but why not emulate COMMIT / ROLLBACK statements with this package: http://pear.php.net/package/DB http://pear.php.net/manual/en/package.database.db.db-common.commit.php Should be do-able even if there's multiple MySQL DBs involved. The main restriction is that you need to use InnoDB format... -- Teach a man to fish... NEW? | http://www.catb.org/~esr/faqs/smart-questions.html STFA | http://marc.theaimsgroup.com/?l=php-general&w=2 STFM | http://php.net/manual/en/index.php STFW | http://www.google.com/search?q=php LAZY | http://mycroft.mozdev.org/download.html?name=PHP&submitform=Find+search+plugins
Attachment:
signature.asc
Description: OpenPGP digital signature
