Refactored WordPressDatabaseHandler to use Log Store Service

Replaces direct usage of DatabaseEntity with LogStoreService in WordPressDatabaseHandler. This change centralizes log entity creation and storage, improving maintainability and consistency.

Author: colinmurphy

plugins/wpgraphql-logging/src/Logger/Handlers/WordPressDatabaseHandler.php

@@ -7,7 +7,7 @@
 use Monolog\Handler\AbstractProcessingHandler;
 use Monolog\LogRecord;
 use Throwable;
-use WPGraphQL\Logging\Logger\Database\DatabaseEntity;
+use WPGraphQL\Logging\Logger\Store\LogStoreService;
 
 /**
  * WordPress Database Handler for Monolog
@@ -27,16 +27,15 @@ class WordPressDatabaseHandler extends AbstractProcessingHandler {
 	 */
 	protected function write( LogRecord $record ): void {
 		try {
-			$entity = DatabaseEntity::create(
+			$log_service = LogStoreService::get_log_service();
+			$log_service->create_log_entity( // phpcs:ignore WordPress.NamingConventions.ValidFunctionName.MethodNameInvalid
 				$record->channel,
 				$record->level->value,
 				$this->get_record_name( $record ),
 				$record->message,
 				$record->context ?? [],
 				$record->extra ?? []
 			);
-
-			$entity->save();
 		} catch ( Throwable $e ) {
 			do_action( 'wpgraphql_logging_write_database_error', $e, $record );
 			if ( defined( 'WP_DEBUG' ) && WP_DEBUG ) {