Description

This PR addresses an issue where the executeQuery method was used for data modification (write) operations in the codebase. According to Doctrine DBAL documentation, executeQuery should only be used for data retrieval, while executeStatement must be used for any operation that modifies data (e.g., INSERT, UPDATE, DELETE, DDL). Using executeQuery for writes can cause replication issues in primary-replica setups, potentially leading to data inconsistencies and errors such as duplicate keys.

What was changed:

• Replaced all instances of executeQuery used for data modification with executeStatement.
• Ensured that all write operations now use the correct method, preventing accidental writes to replica databases.

📋 Steps to test this PR:

1. Test with replication enabled:

• Set up a primary-replica database configuration by adding a replica database host to your local.php config using the db_host_ro key.
• Perform actions in Mautic that trigger data modification (e.g., run a campaign, anonymize IP addresses, remove event logs):
• Create and run a campaign
• Generate the campaign summary - ddev exec php bin/console mautic:campaign:summarize
• Delete the campaign
• Delete unused IP addresses - ddev exec php bin/console mautic:unusedip:delete
• Anonymize all IP adderesses - ddev exec php bin/console mautic:anonymize:ip
• Verify that all data modification queries are executed on the primary database and not the replica.
• Check for the absence of replication errors (such as duplicate key errors) in your database logs.
• Confirm that data remains consistent between the primary and replica databases.

2. Test without replication (single database):

• Use a standard single-database setup without configuring a replica in local.php.
• Perform actions in Mautic that trigger data modification (e.g., run a campaign, anonymize IP addresses, remove event logs):
• Create and run a campaign
• Generate the campaign summary - ddev exec php bin/console mautic:campaign:summarize
• Delete the campaign
• Delete unused IP addresses - ddev exec php bin/console mautic:unusedip:delete
• Anonymize all IP adderesses - ddev exec php bin/console mautic:anonymize:ip
• Ensure that all affected features work as expected and that there are no errors or regressions in functionality.
• Confirm that data is correctly updated in the database.