>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #241467. --> Reported by: [solotandem](https://www.drupal.org/user/240748) >>> <p>Here is a test for the dblog module.</p> <p>I found the following issues:</p> <p>1) The <code>drupalCreateUser</code> function does not trigger an Add User event logging. Should it?<br> 2) Likewise, the <code>drupalCreateNode</code> function does not trigger an Add Content-Type event logging. Should it?<br> 3) When a user is deleted, any content they created remains but the uid = 0. One side effect is their blog entry shows as "'s blog" on the home page. Is this intended or should the content be deleted or 'reassigned' in some fashion?<br> 4) The following query leaves an extra row in the watchdog table. In other words, if dblog_row_limit = 100, the watchdog table will have 101 rows after this function runs. A where clause of 'wid &lt;= %d' (replace '&lt;' with '&lt;=') would leave 100 rows.</p> <php> <div class="codeblock"> <pre><span style="color: #000000"><span style="color: #0000BB">&lt;?php<br></span><span style="color: #007700">function </span><span style="color: #0000BB">dblog_cron</span><span style="color: #007700">() {<br>&nbsp; </span><span style="color: #FF8000">// Cleanup the watchdog table<br>&nbsp; </span><span style="color: #0000BB">$max </span><span style="color: #007700">= </span><span style="color: #0000BB">db_result</span><span style="color: #007700">(</span><span style="color: #0000BB">db_query</span><span style="color: #007700">(</span><span style="color: #DD0000">'SELECT MAX(wid) FROM {watchdog}'</span><span style="color: #007700">));<br>&nbsp; </span><span style="color: #0000BB">db_query</span><span style="color: #007700">(</span><span style="color: #DD0000">'DELETE FROM {watchdog} WHERE wid &lt; %d'</span><span style="color: #007700">, </span><span style="color: #0000BB">$max </span><span style="color: #007700">- </span><span style="color: #0000BB">variable_get</span><span style="color: #007700">(</span><span style="color: #DD0000">'dblog_row_limit'</span><span style="color: #007700">, </span><span style="color: #0000BB">1000</span><span style="color: #007700">));<br>}<br></span><span style="color: #0000BB">?&gt;</span></span></pre></div> </php> 5) In checking the cron functionality, there appears to be something funny with the <code>global $conf</code> array. I noticed this when setting the dblog_row_limit variable by a post from the related administrative form. Based on my tests, there would appear to be multiple copies of the array in memory. <p>I base this on dumping values from the <code>variable_set</code> and <code>variable_get</code> routines before and after setting the dblog_row_limit variable by a post from the administrative form. The <code>$conf[$name]</code> variable has the new value in the set routine, but has the 'system' value in the get routine (called immediately after). By 'system' value, I mean the value when the SimpleTest is not running.</p> <p>Later, I manually called the <code>variable_set</code> routine and this value took.</p> >>> [!note] Pre-migration files - [dblog.test](https://www.drupal.org/files/issues/dblog.test) >>>