in reply to Using Perl and MySQL for Activity Log

Use a database-level trigger for creating the change_log entries. That way the integrity and completeness of the log is enforced at a database layer, and works fine even if someboy uses something else than your perl script to make changes to the catalog table.

Replies are listed 'Best First'.
Re^2: Using Perl and MySQL for Activity Log
by bart (Canon) on Apr 27, 2011 at 10:40 UTC
    That's the best way, in theory.

    However, he is using MySQL. Does his version of Mysql support triggers? I think the newer versions do, but he doesn't say what version of Mysql he is using. (Yes, triggers have been added in 5.0.2.)

    There's a reason why Mysql is traditionally considered a toy database, and this is one of them.