| Bug #77679 | Add read-only connection option (use start transaction read only) | ||
|---|---|---|---|
| Submitted: | 10 Jul 2015 9:58 | ||
| Reporter: | Pavel Cibulka | Email Updates: | |
| Status: | Open | Impact on me: | |
| Category: | MySQL Server: Connection Handling | Severity: | S4 (Feature request) |
| Version: | 5.6 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | read-only connection | ||
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.047 sec. using MySQL 8.4.5-u4-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2025, Oracle Corporation and/or its affiliates
Description: Add read only connection option. This could be based on 5.6 "START TRANSACTION READ ONLY". Add this property to connectors (J Connector etc). Benefits - performance (server will know that all transactions are read only - similar to "START TRANSACTION READ ONLY") - security (no unwanted DELETE etc., this is usually done by read only user in apps - no need to create new user) - easier development for programmers use two connection pools - write pool for UPDATE etc - read pool for SELECT, no additional code needed for "START TRANSACTION READ ONLY" How to repeat: This is Feature request. Suggested fix: Read only connection can use code for "START TRANSACTION READ ONLY" for every transaction initialized by this connection.