If you receive errors like: "This server version doesn't support 'READ WRITE' and 'READ ONLY'. Minimum 5.6.5 is required" with versions of MariaDB that DO support them, this is due to an internal check in mysqli conflicting with a hack in MariaDB to allow replication with oracle mysql.
MariaDB prefixes its server version numbers with "5.5.5-" for example "5.5.5-10.3.7-MariaDB-1:10.3.7+maria~stretch". This is because oracle mysql would interpet the "10" as version 1. Mysql clients aware of MariaDB have been updated to detect and strip this prefix.
However the check for mysqli.begin-transaction sees the 5.5.5 prefix and so fails.
The workaround is to specify a custom version string without the prefix for MariaDB on the command line using the --version option. Then mysqli.begin-transaction functions as expected.
mysqli::begin_transaction
mysqli_begin_transaction
(PHP 5 >= 5.5.0)
mysqli::begin_transaction -- mysqli_begin_transaction — Starts a transaction
說明
物件導向風格 (method):
public bool mysqli::begin_transaction
([ int
$flags
[, string $name
]] )程序化風格:
Warning
此函式目前沒有參考文件；只有引數列表。
參數
-
link -
Procedural style only: A link identifier returned by mysqli_connect() or mysqli_init()
-
flags -
-
name -
回傳值
如果成功則回傳 TRUE，失敗則回傳 FALSE。
參見
- mysqli_autocommit() - Turns on or off auto-committing database modifications
- mysqli_commit() - Commits the current transaction
- mysqli_rollback() - Rolls back current transaction
add a note
User Contributed Notes 4 notes
Ral ¶
5 years ago
PHP Guru ¶
4 years ago
MySQL 5.6 introduces READ ONLY mode which applies optimizations to your transactions that can only be applied when it knows in advance that no table modifications will be made and that no locks will be issued.
The default access mode is READ WRITE in all versions up to and including MySQL 5.6. Starting in MySQL 5.7, the appropriate access mode is detected automatically. So if your transaction attempts modifications or table locks, it will automatically use READ WRITE mode, otherwise it will use READ ONLY mode and your transaction will benefit from the optimizations that come from that without having to explicitly declare is as READ ONLY.
Therefore the only time you need to explicitly declare an access mode is when you are using MySQL 5.6 and you are sure that you want READ ONLY mode. Note that any queries that attempt to modify tables or issue locks in READ ONLY mode will fail. Temporary tables can still be modified.
(Moderators. This post should replace the previous post that I made on the subject. Thanks.)
VasK@hapir ¶
5 years ago
The above answer from Ral worked for us, Thanks a lot. This is how we implemented the proposed workaround for
Warning: mysqli_begin_transaction(): This server version doesn't support 'READ WRITE' and 'READ ONLY'. Minimum 5.6.5 is required
We appended the following line to /etc/my.cnf and restarted MySQL server
version=10.2.19-MariaDB
