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: firebird_sdbc error: *Use of external file at location /home/robby/ext_log.txt is not allowed by server configuration caused by 'INSERT INTO "EXT_LOG" ("C") VALUES ('y');' All tested under OpenSUSE 15.1 64bit rpm Linux with LO 6.4.6.2 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 bug 51780 bug 116968 bug 116970
(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).
Dear avsharapov, 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
Bug still exists with LO 7.4.3.2 on OpenSUSE 15.3 64bit rpm Linux.
This issue combined two different problems. 1. Hang/crash. 2. Missing intl (charset/collation) data. We simply do not bundle anything needed by embedded Firebird, except ifbclient.dll and Engine12.dll; so we don't e.g. bundle intl/ with its fbintl.conf and fbintl.dll, so we only have a handful of embedded charsets, no WIN1251. I will address the first here, and file the other one separately.
https://gerrit.libreoffice.org/c/core/+/170790
Note that testing on Linux is irrelevant for both issues here *at this stage*, because on Linux, likely a system Firebird is used; and there, neither crash nor missing intl data happen. What we see there is likely the next stage, when we will fix the first part specific to Windows (no idea if TDF build for Linux is affected). Then we will see if/why the *succeeded* DDL command results in following failures, as shown in comment 1.
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1edfbb310889d18cdd19aa8b339a510ffb25cf66 tdf#136637: handle SQLException in OStatementBase::disposing It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
After this hang/crash problem is saved, as well as bug 162115 about missing intl data, it is possible to execute: CREATE TABLE mytable (c char(2) character set WIN1251) It is still impossible to create external file tables, exactly because of the missing "server" configuration permission, as noted in comment 1 on Linux. If needed, you can file a separate bug report for that issue (now common for all platforms). Note that this is controlled by ExternalFileAccess setting in an optional firebird.conf file; its template is available if FB repo [1]. Note the text in the setting explanation: # NOTE: THE EXTERNAL TABLE ENGINE FEATURE COULD BE USED TO COMPROMISE # THE SERVER/HOST AS WELL AS DATABASE SECURITY!! # # IT IS STRONGLY RECOMMENDED THAT THIS SETTING BE USED TO LIMIT # EXTERNAL TABLE LOCATIONS! To me, it is unclear if we should somehow expose this functionality in LibreOffice. But of course, depends on the use case and extent of demand. [1] https://github.com/FirebirdSQL/firebird/blob/master/builds/install/misc/firebird.conf
(In reply to Mike Kaganski from comment #16) > It is still impossible to create external file tables, exactly because of > the missing "server" configuration permission, as noted in comment 1 on > Linux. If needed, you can file a separate bug report for that issue (now > common for all platforms). > > Note that this is controlled by ExternalFileAccess setting in an optional > firebird.conf file; its template is available if FB repo [1]. > This can be bypassed just creating the firebird.conf in the program folder and configuring ExternalFileAccess = Full > To me, it is unclear if we should somehow expose this functionality in > LibreOffice. But of course, depends on the use case and extent of demand. > I don't think we should expose it. If somebody with the knowledge need it, only need to add and configure the firebird.conf file, and if don't have the knowledge, is better not to make it easy for them to configure and break something.
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-24-8": https://git.libreoffice.org/core/commit/c245557c4e99ec77c40f493cf7658c1ee0f7eefe tdf#136637: handle SQLException in OStatementBase::disposing It will be available in 24.8.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.