| Summary | Updating preferences are not committed on InnoDB tables |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 3. High |
| Owners | jan (at) horde (dot) org |
| Requester | claude.tompers (at) restena (dot) lu |
| Created | 01/06/2012 (4940 days ago) |
| Due | |
| Updated | 01/25/2012 (4921 days ago) |
| Assigned | |
| Resolved | 01/25/2012 (4921 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
[jan] Use separate database connection for SQL session handler (
Bug #10906).2 files changed, 4 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/1d280685e99dec37d5b82eaa43eb2036b22b159d
Queue ⇒ Horde Framework Packages
We need to start a transaction too, when reconnecting during session
write (
Bug #10906).2 files changed, 3 insertions(+), 2 deletions(-)
http://git.horde.org/horde-git/-/commit/959cddc8a37e48ef8643a03db2a75cd6d58f0de3
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Updating preferences are not committed on InnoDB tables
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
of session handling queries happen as well as the actual UPDATE
horde_prefs query.
All these queries seem to be handled by the same Horde_Db_Adapter_Mysqli
instance. Immediately after the UPDATE query, the Adapter is closed
without committing to the database, therefore the changes are not applied.
The session handler needs a separate DB connection.