Description: After migrating an HSQLDB Base file to Firebird, a link present (master/slave) generates an error in LO 6.1 alpha1. This same converted Base file can be opened in LO v6.02 and works. Steps to Reproduce: 1. Use Base file converted to Firebird 2. Open form containing master/slave link Actual Results: Error generated (see attached) Expected Results: Link data between form and subform Reproducible: Always User Profile Reset: No Additional Info: Base file used was that generated after conversion (see bug 117588) Copy attached. LO version used: Version: 6.1.0.0.alpha1 Build ID: cb47f0d320994e001bc38dc2ee9b7d957b15e6ab CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group error generated - see attachment. This same Base file can be opened using: Version: 6.0.2.1 Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group and the form works without error. User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36
Created attachment 142060 [details] Converted to Firebird Base file
Created attachment 142061 [details] Error generated
I can confirm that the form does work in 6.1, and that it does work as expected under 6.0.3. (64bit linux both) Attempting to create a form in 6.1 (firebird sdbc) from scratch fails also, so not really a migration script error IMO. I think there is an issue for the sub form bug already, I'll look for it and tag this to that if so.
I don't see an earlier bug report for this, so setting this to new. Same error code is displayed whether the form was made before migration or a simpler form using a link field afterwards: firebird_sdbc error: *Dynamic SQL Error *SQL error code = -206 *Column unknown *LINK_FROM_ID *At line 1, column 72 caused by 'isc_dsql_prepare'
Hmm... /me thinks the migration needs to set the "ParameterNameSubstitution" parameter. See https://bugs.documentfoundation.org/show_bug.cgi?id=117053#c15
*** Bug 117856 has been marked as a duplicate of this bug. ***
This is basically the same problem as in bug 117053. based on comment 5, adjusting summary...
Hi Julien, is this issue also fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=c179e8a7ea273a48713192c3ba7dfea313149cd8 ??
(In reply to Xisco Faulí from comment #8) > Hi Julien, > is this issue also fixed by > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=c179e8a7ea273a48713192c3ba7dfea313149cd8 ?? To sum up Lionel's comments here or on gerrit 1) I must check that if I change the substitution parameter for the file either by unzipping the file, changing a content, rezipping... or by using the macro proposed by Lionel, I won't reproduce the buggy behaviour. If this is ok, it means the patch is ok but only for the new created files. 2) Lionel proposed another idea which consists to bypass the value in the file. This must be tested. It'd allow to have the right result even with old files (I mean files created before the patch pushed on master, so 99,99999999999% of them :-) ) 3) Finally, this patch or the both patch should be at minimum on master + 6.1 branch. I'd like also see this/them on 6.0 branch. In brief, I'd say it's not yet fixed. Hope it's clear + I didn't misunderstand Lionel's view :-)
Argh! thought it was 118112 (so for mysql) Forget my previous message, I must take a real look here.
Xisco: The quoted patch concerns odb linked with Mysql DBs only so it doesn't fix this one. I don't know how to fix this but according to Lionel's comment 5, the patch is expected to be quite different as the one you quoted since it's the migration part which must be changed. Very sorry for the confusion triggered by my comment 9.
*** Bug 121477 has been marked as a duplicate of this bug. ***
*** Bug 122515 has been marked as a duplicate of this bug. ***
*** Bug 125856 has been marked as a duplicate of this bug. ***
Do we really want to set the migration from "experimental" to "non experimental" in LO 6.3, if this bug isn't solved? The migration will run and we will get many feedbacks about forms with subforms, which do not run, queries with parameters, which do not run ...
(In reply to Robert Großkopf from comment #15) > Do we really want to set the migration from "experimental" to "non > experimental" in LO 6.3, if this bug isn't solved? > ... AFAIC, whole Firebird part should be experimental. See discussion here: http://document-foundation-mail-archive.969070.n3.nabble.com/Base-without-HSQL-support-td4262421.html The more the time goes by the more the lack of expert dev resources in Base becomes crucial.
(In reply to Robert Großkopf from comment #15) > Do we really want to set the migration from "experimental" to "non > experimental" in LO 6.3, if this bug isn't solved? > > The migration will run and we will get many feedbacks about > forms with subforms, which do not run, > queries with parameters, which do not run ... The issue is designated as major and I suppose someone could make a point of pointing out to the ESC that this should be treated as a show stopper for a release. The fix should address both this use case and the form/subform use case, at least I would expect it is a common code issue. On the other hand both situations should be really easy to fix after the fact also, it's a couple lines of basic (copy past and run once) would fix it permanently for effected files, IIRC.
Dear Stang, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists in LO 7.4.6.2 on OpenSUSE 15.4 64bit rpm Linux.