Bug 139611 - FILESAVE: LibreOffice Base doesn't retain column formats on file save for PostgreSQL connected databases
Summary: FILESAVE: LibreOffice Base doesn't retain column formats on file save for Pos...
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.0.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-14 15:46 UTC by Denis Sbragion
Modified: 2023-11-19 20:22 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Denis Sbragion 2021-01-14 15:46:49 UTC
Description:
Hello,

this is a long lasting nuisance of Base when PostgreSQL databases are used, with somewhat different behaviour from version to version. Whenever some format is applied to a column, either dates, percentages or other numeric fields, under some circumnstances the formatting get lost after saving, closing and reopening the Base file.

Since version 7 the behaviour seem to have become somewhat stable, in the sense that any previous formatting get lost on save for any table which is not currently open. I.e. apply some formatting to table A, then save and close the file, open again, apply some formatting to table B without opening table A, save and close again, reopen, formatting on table B is retained, formatting on table A get lost most of the times.

With previous versions the behaviour was somewhat erratic, with some versions seldom losing any formatting and others loosing almost everything on every save. Don't remeber exactly which version was better and which one was worse, but I'm sure there have been some which had almost no problems.

Hope it helps, and thanks for this excellent software.

Steps to Reproduce:
1. Create a Base file connected to a PostgreSQL DB with at least two tables, let's say A and B, with columns which could be formatted (date or numeric columns for example)
2. Open table A and apply some formatting to a column
3. Save while table A is open then close the file
4. Open the file again
5. Open table B without opening table A and apply some formatting
6. Save while table B is open and close the file
7. Open the file again
8. Open table A and you will see that the preciously applied formatting get lost most of the times

Actual Results:
Applied formatting get lost.

Expected Results:
Applied formatting is retained between subsequent saves.


Reproducible: Sometimes


User Profile Reset: No



Additional Info:
Version: 7.0.1.2 (x64)
Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: it-IT (it_IT); Interfaccia utente: it-IT
Calc: threaded

I never checked if this happens also on Linux. Could do it if needed. Didn't try to reset the UserProfile, but over the years this problem happened on at least three different computers and even after few reinstalls, so I doubt it could be a UserProfile issue.
Comment 1 Robert Großkopf 2021-07-14 09:51:10 UTC
Have tested this with OpenSUSE 15.2 64bir rpm Linux and LO 7.2.0.1.
Using the direct connection here.

First I had problems to create a field for a date which I could format afterwords. When I don't format the field for a date when creating the table the field seem to be recognized from Base only as a field for text.

Then I created another table with a field, which could be formatted later with a currency-format.

I opened  table a, put in some data, changed the formatting of a field, closed the table.
Same with table b.
Reopened the table a and the changed formatting appears.
Then I closed the database file and closed LO.
Reopened LO and opened the database file.
Format is the format I have chosen before.

When opening the odb-file I could see: The styles are saved in the content.xml-file inside the odb-file
 
All this is detected with Linux and direct connection.

Which connection do you use?
Comment 2 Denis Sbragion 2021-07-14 10:29:12 UTC
Hello Robert,

thanks for your feedback. I'm using a direct connection too, i.e. no ODBC/JDBC involved. BTW I'm under Windows 7, LO version:

Version: 7.1.3.2 (x64) / LibreOffice Community
Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: it-IT (it_IT); UI: it-IT
Calc: threaded

I never tried under Linux. I'll do it as soon as possible with the same database to see what happens. I have a Debian installation, which usually is a bit lagging WRT the latest release, but it could be of help anyway.

Bye,

Denis Sbragion
Comment 3 Denis Sbragion 2021-07-14 11:09:59 UTC
Tested right now under Debian Buster, LO Version 6.1.5.2, and I confirm that in this environment it works as expected.

I want to do one further test under Windows, because so far I always opened the database from an SMB network share and never tried from a local disk. But I have to switch to Windows again, so I'll add one further comment for this test.
Comment 4 Denis Sbragion 2021-07-14 11:30:08 UTC
Tested again under Windows, but with the database file on a local disk. The formatting of unopened tables get lost on save, so it isn't a matter of network share vs local disk.

Feel free to contact me again if you need some further help.

Bye,

Denis Sbragion
Comment 5 QA Administrators 2021-07-15 03:37:24 UTC Comment hidden (obsolete)
Comment 6 Denis Sbragion 2023-05-18 08:38:05 UTC
Hello,

just an update, this nuisance presists on the latest version:

Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: it-IT (it_IT); UI: it-IT
Calc: threaded

Bye,