<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Purging the audit log tables using the posted example? in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/purging-the-audit-log-tables-using-the-posted-example/m-p/324224#M11225</link>
    <description>&lt;P&gt;I have been using a description of a SQL purge function outlined &lt;A href="http://doc.nuxeo.com/x/kAnF"&gt;here&lt;/A&gt; as the basis for a SQL function to purge the event log (nxp_logs) by username and date.&lt;/P&gt;
&lt;P&gt;It appears the example deletes entries in the nxp_log, nxp_logs_extinfo and nxp_logs_mapextinfos tables using a temporary table based on the references to nxp_logs table contained in the nxp_logs_extinfos and nxp_extinfo tables. The temporary table is used as the baseline list of what to delete in each of the three tables above.&lt;/P&gt;
&lt;P&gt;If an entry in the nxp_logs table does not have a link in the nxp_logs_mapextinfos or the nxp_logs_extinfo tables then that entry on nxp_logs will not be deleted even though it might meet the data criteria used when creating the original temporary "baseline" table.&lt;/P&gt;
&lt;P&gt;Question: Do I need to make another "delete" pass through the nxp_log table after the "delete" pass based on the temporary table build originally to delete the entries which meet the  purge criteria and do NOT have references to the nxp_logs_mapextinfos table?&lt;/P&gt;
&lt;P&gt;I've looked through the nxp_log table and some of the entries in the table are NOT referenced by the nxp_logs_mapextinfos table and therefore are not picked up in the baseline temporary table.&lt;/P&gt;
&lt;P&gt;Thanks, in advance for any SQL insights you may have.&lt;/P&gt;
&lt;P&gt;Karl&lt;/P&gt;</description>
    <pubDate>Thu, 21 Feb 2013 18:16:04 GMT</pubDate>
    <dc:creator>karl_harris_</dc:creator>
    <dc:date>2013-02-21T18:16:04Z</dc:date>
    <item>
      <title>Purging the audit log tables using the posted example?</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/purging-the-audit-log-tables-using-the-posted-example/m-p/324224#M11225</link>
      <description>&lt;P&gt;I have been using a description of a SQL purge function outlined &lt;A href="http://doc.nuxeo.com/x/kAnF"&gt;here&lt;/A&gt; as the basis for a SQL function to purge the event log (nxp_logs) by username and date.&lt;/P&gt;
&lt;P&gt;It appears the example deletes entries in the nxp_log, nxp_logs_extinfo and nxp_logs_mapextinfos tables using a temporary table based on the references to nxp_logs table contained in the nxp_logs_extinfos and nxp_extinfo tables. The temporary table is used as the baseline list of what to delete in each of the three tables above.&lt;/P&gt;
&lt;P&gt;If an entry in the nxp_logs table does not have a link in the nxp_logs_mapextinfos or the nxp_logs_extinfo tables then that entry on nxp_logs will not be deleted even though it might meet the data criteria used when creating the original temporary "baseline" table.&lt;/P&gt;
&lt;P&gt;Question: Do I need to make another "delete" pass through the nxp_log table after the "delete" pass based on the temporary table build originally to delete the entries which meet the  purge criteria and do NOT have references to the nxp_logs_mapextinfos table?&lt;/P&gt;
&lt;P&gt;I've looked through the nxp_log table and some of the entries in the table are NOT referenced by the nxp_logs_mapextinfos table and therefore are not picked up in the baseline temporary table.&lt;/P&gt;
&lt;P&gt;Thanks, in advance for any SQL insights you may have.&lt;/P&gt;
&lt;P&gt;Karl&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2013 18:16:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/purging-the-audit-log-tables-using-the-posted-example/m-p/324224#M11225</guid>
      <dc:creator>karl_harris_</dc:creator>
      <dc:date>2013-02-21T18:16:04Z</dc:date>
    </item>
  </channel>
</rss>

