Hi, I was wondering if there was a preferred method of doing auditing of database tables within Turbine? I haven't seen anything in the docs so was wondering if anyone had any pointers on an approach that worked well. Currently I am thinking of extending each database table that requires auditing as follows: <table name="table1"> <column name="CREATEDBY" type="VARCHAR" /> <column name="CREATEDDATE" type="Date" /> <column name="MODIFIEDBY" type="VARCHAR" /> <column name="MODIFIEDDATE" type="Date" /> <column name="DELETEDBY" type="VARCHAR" /> <column name="DELETEDDATE" type="Date" /> <column name="APPROVEDBY" type="VARCHAR" /> <column name="APPROVEDDATE" type="Date" /> <column name="STATUS" type="VARCHAR" /> <column name="VERSION" type="INTEGER" /> ... </table> Anyway, I was wondering if anyone has any ideas on how this type of functionality might be incorporated into Torque. That way tables could be flagged as needing an audit in the database schema, and Torque generate the necessary code. Any ideas or pointers would be greatly appreciated. Jon North -------------------------------------------------- DISCLAIMER: This message contains proprietary information some or all of which may be confidential and/or legally privileged. It is for the intended recipient only who may use and apply the information only for the intended purpose. Internet communications are not secure and therefore the British Biotech group does not accept legal responsibility for the contents of this message. Any views or opinions presented are only those of the author and not those of the British Biotech group. If you are not the intended recipient please delete this e-mail and notify the author immediately by calling ++44 (0)1865 748747; do not use, disclose, distribute, copy, print or rely on this e-mail. ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
