Missing alogin_user_settings table primary key

Created on 17 March 2025, about 2 months ago

Problem/Motivation

The alogin_user_settings table is missing the primary key which is required for READ COMMITTED transaction isolated level to work correctly.

Steps to reproduce

Check the alogin_schema() function in the alogin.install file, and observe no primary key defined.
This can also be seen by inspecting the database table schema after the module is installed.

Proposed resolution

Add uid as a primary key.

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

None. The uid field is de-facto already used as a unique row identifier across the code. Also, adding a primary key would have a positive performance impact.

πŸ› Bug report
Status

Active

Version

2.1

Component

Code

Created by

πŸ‡ΊπŸ‡¦Ukraine abramm Lutsk

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024