Bug 146568 - LO fails to apply HSQL 2.6 privileges
Summary: LO fails to apply HSQL 2.6 privileges
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.2.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-04 17:33 UTC by Andreas Säger
Modified: 2024-01-06 03:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
odb document with external database and HSQL drivers (5.81 MB, application/zip)
2022-01-04 17:33 UTC, Andreas Säger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Säger 2022-01-04 17:33:01 UTC
Created attachment 177309 [details]
odb document with external database and HSQL drivers

See https://forum.openoffice.org/en/forum/viewtopic.php?f=40&t=106762

1) Download the attached zip to a trusted directory. It contains a database document, a database in a subdirectory and 3 hsqldb driver files..
The database contains an auto-install macro connecting the document to the database and to the hsqldb.jar. hsqldb.jar is identical to hsqldb-2.5.1.jar.

2) Open the database document. The auto-installer macro should display 2 messages about successful connection to driver and database.

3) Go to the tables section and confirm user "U1".

4) Open the Persons table. Edit a forename and save the record. This is the only editable field of this table. 

5) Open the other table it is editable.

6) Shut down the entire office suite.

7) In the driver subdirectory replace hsqldb.jar with a copy of (or symlink to) hsqldb-2.6.1.jar which is the latest HSQL driver.

8) Repeat 2) 3) 4) 5). Both tabls are read-only. They should behave as in steps 4) and 5).

The problem occurs with LO and AOO only. It does not occur with other database frontends.
Comment 1 Alex Thurgood 2022-01-05 08:50:47 UTC
Reproduced and confirming with

Version: 7.2.1.2 / LibreOffice Community
Build ID: 87b77fad49947c1441b67c559c339af8f3517e22
CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR
Calc: threaded
Comment 2 Alex Thurgood 2022-01-05 09:15:15 UTC
FWIW, I ran a LLDB debug session to compare the behaviour when opening the ODB file with each driver in the daily master build:

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 9cc3672a4d7e9c9a647d388dba493bbb28d96da2
CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded

With hsqldb-2.5.1.jar, this is what I see when I open any of the tables:


Jan 05, 2022 10:04:14 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache open start
Jan 05, 2022 10:04:14 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache open end
warn:dbaccess:46779:1449704:dbaccess/source/core/dataaccess/ModelImpl.cxx:923:  com.sun.star.container.NoSuchElementException
warn:dbaccess:46779:1449704:dbaccess/source/core/dataaccess/ModelImpl.cxx:923:  com.sun.star.container.NoSuchElementException
Jan 05, 2022 10:05:45 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache commit start
Jan 05, 2022 10:05:45 AM org.hsqldb.persist.Logger logInfoEvent
INFO: dataFileCache commit end
Jan 05, 2022 10:05:45 AM org.hsqldb.persist.Logger logInfoEvent
INFO: Database closed



With hsqldb-2.6.1.jar, I don't get any such output, the console remains blank. 

Would that be in any way related to this:

https://stackoverflow.com/questions/9931156/is-there-a-way-to-silence-hsqldb-logging

i.e. has someone in the hsqldb project deactivated logging in some way for version 2.6.1, or is the call to logging of the transactions in some way not activated within LO, for whatever reason ?
Comment 3 QA Administrators 2024-01-06 03:13:44 UTC
Dear Andreas Säger,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug