Bug 137539 - Problem in the SQL of LibreOffice Base
Summary: Problem in the SQL of LibreOffice Base
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.3.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-16 15:59 UTC by ASHIK ACHARYA
Modified: 2020-10-17 07:29 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 ASHIK ACHARYA 2020-10-16 15:59:57 UTC
Description:
I have been using LibreOffice Base for around a month now. When I am working with the Base using the SQL, sometimes I need to erase the previous codes just for some space. After erasing all the text (code), if I press delete key just once, LibreOffice crashes all of a sudden. In that SQL section, if we continuously press the delete key to erase all text, LibreOffice crashes all of a sudden. And to add to the plight, many times the data does not recover. 

Actual Results:
Please go to the 'Tools' of the LibreOffice Base. Go to SQL and start writing some code. Try to erase the text by pressing the delete key. You will have to press continuously to delete all the text. If you keep on pressing just a second after all the text has been deleted, LibreOffice base will close unexpectedly.

Expected Results:
LibreOffice Base crashes (closes unexpectedly)


Reproducible: Always


User Profile Reset: No



Additional Info:
LibreOffice should not had crashes. If delete key would denote closing then software should have asked whether or not I wanted to close. And asked whether or not I wanted to save the document before closing.
Comment 1 Julien Nabet 2020-10-16 20:54:46 UTC
Could you give a try to 6.4.6 or brand new 7.0.2?

Which database type you use? Embedded HSQLDB, Mysql, other?

If you still reproduce this, could you attach an example file so we can try to reproduce this?
Comment 2 ASHIK ACHARYA 2020-10-17 07:20:57 UTC
I just checked on the latest version 7.0.2 and there was no such bug. However, in the previous version (6.3.4.2), there is still that problem. I used the Embedded HSQLDB database. Even the version 6.3.4.2 is not that old and could still be used by many users. So this bug has to be addressed as quickly as possible.
Comment 3 Julien Nabet 2020-10-17 07:29:30 UTC
(In reply to ASHIK ACHARYA from comment #2)
> I just checked on the latest version 7.0.2 and there was no such bug.
> However, in the previous version (6.3.4.2), there is still that problem. I
> used the Embedded HSQLDB database. Even the version 6.3.4.2 is not that old
> and could still be used by many users. So this bug has to be addressed as
> quickly as possible.

No, 6.3 branch is EOL. There won't be any official TDF new release of 6.3.
You can also try 6.4.6, there may be the pb here too but there's slight chance to fix it for 6.4.7 the last release of 6.4 branch (see https://wiki.documentfoundation.org/ReleasePlan/6.4)