go to post Janzai Renato · Jan 3 If you want an account with only read access to be unable to initiate transactions, you can do so through the following methods: 1. * * Database level restrictions * *: *Most database management systems (such as MySQL, PostgreSQL, SQL Server, etc.) allow you to set permissions for accounts or roles. You can set permissions for the service account to prevent it from initiating transactions. *For example, in MySQL, you can use the 'SET TRANSACTION' statement to set the isolation level of transactions. However, if the account does not have the permission to 'SET TRANSACTION', it will not be able to change the isolation level of the transaction and therefore cannot start the transaction. 2. * * Application level restrictions * *: *If the tool allows changing its behavior through configuration files or settings, you can check if there is an option to disable the automatic start of transactions. *Some tools provide command-line parameters or configuration options that allow you to specify whether to automatically start transactions. Check the documentation of the tool to see if there is such an option. 3. * * Code level limitations * *: *If the tool allows you to interact with it through code or scripts, you can try manually starting a transaction before the query and committing it immediately after the query. In this way, transactions will only exist for a short period of time and will not trigger long running transaction warnings. 4. * * Database monitoring and alerts * *: *Although you cannot prevent the account from initiating transactions, you can set up database monitoring tools to detect long running transactions and send alerts for you. In this way, if the account accidentally initiates a long running transaction, you can receive notification as soon as possible and take action. 5. * * Review and Training * *: *Train the personnel using this account to ensure they understand how to use it correctly and not attempt any operations that they do not have permission to perform. *Consider regularly reviewing the usage of this account to ensure it has not been abused. 6. * * Consider other tools or methods * *: *If existing tools cannot meet your needs, consider finding or developing a new tool that can meet your needs and will not automatically initiate long running transactions. Overall, you need to combine multiple methods to ensure that accounts with only read access do not inadvertently initiate long running transactions.
