Entering the sql command
CREATE TABLE ext_log EXTERNAL FILE 'ext_log.txt' (c char(2) character set WIN1251)
will cause Libreoffice to hang
Tested on Windows7
P.S. I set the severity to minor because it is unlikely that someone will type such a command :)
Seems Firebird doesn't like the character set - definition here.
CREATE TABLE ext_log EXTERNAL FILE 'ext_log.txt' (c char(2));
seems to work with a real path. But I couldn't find the file, which has been created. Then I tried to input values into this (non existent, but listed) table. I will get this message:
*Use of external file at location /home/robby/ext_log.txt is not allowed by server configuration
'INSERT INTO "EXT_LOG" ("C") VALUES ('y');'
All tested under OpenSUSE 15.1 64bit rpm Linux with LO 220.127.116.11
The original command with
character set WIN1251
leads also to a hang of LO.
Created attachment 165374 [details]
bt with debug symbols
On pc Debian x86-64 with master sources updated today, I could reproduce this.
Just for the record since, according to the bt, it seems it's Firebird lib itself which aborts, I don't know how we could avoid the crash here.
Firebird works well with this command.
And and writes characters in the specified encoding.
But apparently LO can't figure out the meta information later.
Please note that my LO fell exactly with the CHARACTER SET option.
Is firebird still relevant? I see that when creating a new database, Firebird is missing from the selection list. This is if advanced mode is not enabled. in 6.3, it was in normal mode.
(In reply to shar from comment #5)
> Is firebird still relevant? I see that when creating a new database,
> Firebird is missing from the selection list. This is if advanced mode is not
> enabled. in 6.3, it was in normal mode.
The internal HSQLDB works better with the GUI of base than the internal Firebird. There are many special bugs only for the internal Firebird database. So it has been put back to an experimental feature.
I didn't find any information about this in the version change texts. But this is very important. It's a pity that the built-in Firebird is again in question. I considered this a big step and a huge plus for LO Base. But nothing do.
I guess I was too hasty. So I urgently need to do a reverse conversion to Hbase and forget about the built-in Firebird. Thank you for the information.
For Firebird please see the meta bugs
(In reply to avsharapov from comment #7)
> I didn't find any information about this in the version change texts. But
> this is very important. It's a pity that the built-in Firebird is again in
> question. I considered this a big step and a huge plus for LO Base. But
> nothing do.
> I guess I was too hasty. So I urgently need to do a reverse conversion to
> Hbase and forget about the built-in Firebird. Thank you for the information.
There's no automatic reverse conversion to HSQLDB. I can only propose you to use backups of your HSQLDB files.
About the lacking information, you're right, it's indeed lacking in release notes. (I put tdf#135882 on cc).
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!
Bug still exists with LO 18.104.22.168 on OpenSUSE 15.3 64bit rpm Linux.