Bug 124773 - VIEWING: External database jdbc hsqldb, Crash in the case of SELECT, SQL query, access to the database. Crash in: sal3.dll
Summary: VIEWING: External database jdbc hsqldb, Crash in the case of SELECT, SQL quer...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Database-Connectivity
  Show dependency treegraph
 
Reported: 2019-04-16 13:37 UTC by Krzysztof
Modified: 2021-04-07 11:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["sal3.dll"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Krzysztof 2019-04-16 13:37:36 UTC
This bug was filed from the crash reporting server and is br-67822be4-36b6-4971-9387-6f7e8995f3db.
=========================================

I'm creating a new, clean external database (HSQLDB version 2.4.1).
Connecting database JDBC:
URL Jdbc: hsqldb:hsql://localhost/xGR
Class Driver: org.hsqldb.jdbcDriver

Login SA.

I enter SQL queries:
CREATE ROLE "normal_user";

CREATE USER "U1" PASSWORD "12345";

CREATE CACHED TABLE "Test2" ("ID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 0) NOT NULL PRIMARY KEY, "name" VARCHAR (100) NOT NULL, "addDateTime" TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL, "updateDateTime" TIMESTAMP NULL);

CREATE TRIGGER PUBLIC. "Test2_TRG" BEFORE UPDATE ON PUBLIC. "Test2" REFERENCING OLD ROW AS OLDROW NEW ROW AS NEWROW FOR EACH ROW SET NEWROW. "updateDateTime" = CURRENT_TIMESTAMP;

GRANT SELECT (ID, "name"), UPDATE (ID, "name"), INSERT (ID, "name") ON TABLE "Test2" TO "normal_user";

GRANT "normal_user" TO "U1";

The commands were completed successfully.
We login in as U1, open the "Test2" table. Total crash Libreoffice.

Normal operation should give an exception.
"user lacks privilege or object not found: Test2 in statement [SELECT * FROM "Test2"] "

Greetings
Comment 1 Alex Thurgood 2019-04-23 09:46:44 UTC
@Krzysztof : just out of interest, which version of JDK are you using ?

From the crash trace, it appears that this is a home built version of LO for Windows ?
Comment 2 Krzysztof 2019-04-23 15:02:17 UTC
(In reply to Alex Thurgood from comment #1)
> @Krzysztof : just out of interest, which version of JDK are you using ?
> 
> From the crash trace, it appears that this is a home built version of LO for
> Windows ?
Java install file "jdk-8u202-windows-x64.exe"

Java in LO: JDK 1.8.0_202
Java in LO: JRE 1.8.0_202 (in LO it was marked in options)

System: Windows 10.
Comment 3 Xisco Faulí 2019-10-21 11:53:01 UTC
Hello Krzysztof,
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 4 QA Administrators 2020-04-19 03:36:57 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2020-05-20 03:41:24 UTC
Dear Krzysztof,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp