Bug 495939

Summary: database regional setting UTF8 versus UTF16SE
Product: [Applications] digikam Reporter: Mir-123
Component: Database-SqliteAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: normal CC: caulier.gilles, metzpinguin, Mir-123
Priority: NOR    
Version First Reported In: 8.4.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: SQL PRAGMA encoding UTF16SE versus Lokale UTF8

Description Mir-123 2024-11-07 20:38:19 UTC 
Why are different regional settings displayed when accessing the same database and database under Help “Database statistics when accessing from Ubuntu and SteamdeckOS? In Ubuntu (Digikamvers. 7.5.0) under database regional setting UTF8 and when accessing via SteamdeckOS (Digikamvers. 8.4.0) UTF16LE. 
The Steam Deck uses SteamOS 3.0 as operating system, which is based on Arch Linux and uses KDE Plasma 5 as desktop environment. 
The aim of my question is that I want to access the QSQLite digicam database alternately from both systems. Unfortunately, this constellation results in messages when starting Digikan due to the different regional settings.
I wanted to avoid the problem by using Digikam as an app image and then using the same version. This should also work with different Linux versions. Is it normal if the database regional setting is still UTF16LE in the database?
Comment 1 Maik Qualmann 2024-11-07 20:57:48 UTC 
We do not set PRAGMA encoding parameters to a SQLite DB. We use the system default. PRAGMA encoding cannot be changed after the DB is created. All operating systems, including Windows or macOS, use the SQLite default UTF-8.
Your two systems use different system settings.

Maik
Comment 2 Mir-123 2024-11-07 23:13:30 UTC 
Created attachment 175632 [details]
SQL PRAGMA encoding UTF16SE versus Lokale UTF8
Comment 3 Mir-123 2024-11-07 23:16:23 UTC 
Thank you for the information. The facts have become a little clearer to me. 
In the DB Browser for SQLite program, the entry UTF-8 is output as the value in the table under settings for keyword locale. Similarly, in the same database using SQL PRAGMA encoding; UTF-16le is output. This apparently caused Digikam to get confused and this constellation resulted in messages when Digikan was started. 
If I have understood you correctly, however, the SQL PRAGMA encoding; query is decisive for the database and the settings for keyword locale (which can theoretically also be changed via the database) are probably only important as a display function.
Comment 4 Maik Qualmann 2024-11-08 06:50:37 UTC 
Correct, the locale in the DB is the last used database PRAGMA encoding.
If this has changed, digiKam will provide the information about it.

Maik
Comment 5 caulier.gilles 2025-04-13 02:27:29 UTC 
MAik,

Another file to close here ?

Gilles