* Updated Database->_age_out_data() to only run once per day, unless explicitely called with --age-out-database.

Signed-off-by: digimer <digimer@gravitar.alteeve.com>

Anvil/Tools/Database.pm

@@ -1329,8 +1329,8 @@ sub connect
 	# We need the host_uuid before we connect.
 	if (not $anvil->data->{sys}{host_uuid})
 	{
-		$anvil->data->{sys}{host_uuid} = $anvil->Get->host_uuid;
-		$anvil->Log->variables({source => $THIS_FILE, line => __LINE__, level => $debug, list => { "sys::host_uuid" => $anvil->data->{sys}{host_uuid} }});
+		$anvil->data->{sys}{host_uuid} = $anvil->Get->host_uuid({debug => 2});
+		$anvil->Log->variables({source => $THIS_FILE, line => __LINE__, level => 2, list => { "sys::host_uuid" => $anvil->data->{sys}{host_uuid} }});
 	}
 	
 	# This will be set to '1' if either DB needs to be initialized or if the last_updated differs on any node.
@@ -17743,6 +17743,25 @@ sub _age_out_data
 	{
 		$anvil->Log->variables({source => $THIS_FILE, line => __LINE__, level => $debug, list => { uuid => $uuid }});
 
+		# Before I proceed, see when the last age-out happened. If it's less than 24 hours ago, don't
+		# bother. Of course, if we've been specfiically asked to age out data, proceed.
+		if (not $anvil->data->{switches}{"age-out-database"})
+		{
+			my ($last_age_out, undef, undef) = $anvil->Database->read_variable({
+				debug         => $debug,
+				variable_name => "database::".$uuid."::aged-out",
+			});
+			$anvil->Log->variables({source => $THIS_FILE, line => __LINE__, level => $debug, list => { last_age_out => $last_age_out }});
+
+			if (($last_age_out) && ($last_age_out =~ /^\d+$/))
+			{
+				my $age = time - $last_age_out;
+				$anvil->Log->variables({source => $THIS_FILE, line => __LINE__, level => $debug, list => { age => $age }});
+
+				next of $age < 86400;
+			}
+		}
+
 		my $queries = [];
 		my $query   = "SELECT job_uuid FROM jobs WHERE modified_date <= '".$old_timestamp."' AND job_progress = 100;";
 		$anvil->Log->variables({source => $THIS_FILE, line => __LINE__, level => $debug, list => { query => $query }});
@@ -17776,6 +17795,17 @@ sub _age_out_data
 			$anvil->Database->write({debug => $debug, uuid => $uuid, query => $queries, source => $THIS_FILE, line => __LINE__});
 		}
 
+		my $variable_uuid = $anvil->Database->insert_or_update_variables({
+			variable_name         => "database::".$uuid."::aged-out",
+			variable_value        => time,
+			variable_default      => "0",
+			variable_description  => "striker_0199",
+			variable_section      => "database",
+			variable_source_uuid  => "NULL",
+			variable_source_table => "",
+		});
+		$anvil->Log->variables({source => $THIS_FILE, line => __LINE__, level => $debug, list => { variable_uuid => $variable_uuid }});
+
 		$anvil->Database->locking({debug => $debug, renew => 1});
 	}
 	

share/words.xml

@@ -3085,7 +3085,7 @@ If you are comfortable that the target has changed for a known reason, you can s
 		<key name="striker_0196">Recipient's Email</key>
 		<key name="striker_0197">The email that alerts are sent to.</key>
 		<key name="striker_0198">The language the user will receive alerts in.</key>
-		<key name="striker_0199"></key>	<!-- free -->
+		<key name="striker_0199">This records when the database was last "aged out". That is to say; When did that last purge of old records happen. Normally, aging out only runs once per day. An age-out can be forced from any command line tool with '--age-out-database'.</key>
 		<key name="striker_0200">The alert level used for new (and existing) #!string!brand_0006!# systems.</key>
 		<key name="striker_0201">Existing alert recipients:</key>
 		<key name="striker_0202">This puts the host into network mapping mode. In this most, most functions are disabled and the link status of network interfaces are closely monitored.</key>