read-committed

MySQL REPEATABLE-READ Workbench transaction level not set

蓝咒 提交于 2019-12-02 08:43:21
问题 We have set the following in the my.ini file [mysqld] transaction-isolation = READ-COMMITTED We assume this setting will be the default for all user sessions. When logging in using PHPMyAdmin the tx_isolation is set correctly and works as expected. However, when connecting to the server using MySQL Workbench 6.0 an examination of the variables shows that the tx_isolation level is set to REPEATABLE-READ. The effects of this isolation level are also as expected. We want to set the transaction

PostgreSQL cannot begin/end transactions in PL/pgSQL

╄→尐↘猪︶ㄣ 提交于 2019-11-27 17:10:15
问题 I am seeking clarification of how to ensure an atomic transaction in a plpgsql function, and where the isolation level is set for this particular change to the database. In the plpgsql function shown below, I want to make sure that BOTH the deletion AND the insertion succeed. I am getting an error when I try to wrap them in a single transaction: ERROR: cannot begin/end transactions in PL/pgSQL . What happens during execution of the function below if another user has added a default behavior