Base should allow fields to be reordered.
This property isn't provided by the internal HSQLDB database. It will only allow to position a new field by SQL: ALTER TABLE "Person" ADD "Forename" VARCHAR(25) BEFORE "Surname"; Internal Firebird (which is experimental at this moment) will allow to position a field after it has been inserted: ALTER TABLE "Person" ALTER "Forename" POSITION 2; But there are also bugs while people are trying to copy and paste with the table editor. Only fieldname and fieldtype where moved, but content will be at the same position of the table … DoN#t know the bug number.
Am I correct to think that Firebird allows this, and HSQLDB is (potentially) unable to provide this? If all of that is true, I suppose that my request is already being completed by the developers of the Experimental Features.
(In reply to BEEDELL ROKE JULIAN LOCKHART from comment #2) > Am I correct to think that Firebird allows this, and HSQLDB is (potentially) > unable to provide this? Firebird allows this in direct SQL, not through the GUI. And Firebird is experimental. HSQLDB only allows to add a new field as a special position in direct SQL, not though GUI. > If all of that is true, I suppose that my request is > already being completed by the developers of the Experimental Features. No, it isn't. Everybody, who tries to get this by GUI with any database (internal Firebird, HSQKDB external databases) by copy and paste of fields or cut and past of fields will see its doesn't work. Use forms for input data. Base is made for this. You could sort fields there independent of sorting in the table.
(In reply to Robert Großkopf from comment #3) > (In reply to BEEDELL ROKE JULIAN LOCKHART from comment #2) > > Am I correct to think that Firebird allows this, and HSQLDB is (potentially) > > unable to provide this? > > Firebird allows this in direct SQL, not through the GUI. And Firebird is > experimental. > HSQLDB only allows to add a new field as a special position in direct SQL, > not though GUI. > > > If all of that is true, I suppose that my request is > > already being completed by the developers of the Experimental Features. > > No, it isn't. Everybody, who tries to get this by GUI with any database > (internal Firebird, HSQKDB external databases) by copy and paste of fields > or cut and past of fields will see its doesn't work. > > Use forms for input data. Base is made for this. You could sort fields there > independent of sorting in the table. Understood. I am new to database-management. You appear to have stated that I should use the form-feature to present the data as I desire, which might well remediate this problem for me. However, does no rationale exist for being able to reorder the fields of the database? Even if this is not useful for me, I do not want to close this report unless this is confirmed to be undesirable. I am thankful for your assistance.
Dear BEEDELL ROKE JULIAN LOCKHART, 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
Created attachment 204316 [details] A Screenshot That Depicts That Firebase Support Is Unavailable In Binary Releases I am unable to confirm that this remains, because I solely see HSQLDB as an available option (rather than Firebase, too) in: > ~~~ > Name : libreoffice-base > Epoch : 1 > Version : 25.8.3.2 > Release : 2.fc43 > Architecture: x86_64 > Install Date: Thu 27 Nov 2025 14:07:05 GMT > Size : 5574829 > Signature : > RSA/SHA256, Thu 13 Nov 2025 21:23:42 GMT, Key ID 829b606631645531 > Source RPM : libreoffice-25.8.3.2-2.fc43.src.rpm > Build Date : Thu 13 Nov 2025 15:11:52 GMT > Build Host : buildhw-x86-08.rdu3.fedoraproject.org > Packager : Fedora Project > Vendor : Fedora Project > ~~~ Due to https://bugs.documentfoundation.org/show_bug.cgi?id=169709#c0, I've nothing newer to confirm with, because I cannot feasibly compile LO.
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #6) > Created attachment 204316 [details] > A Screenshot That Depicts That Firebase Support Is Unavailable In Binary > Releases 2 hints: You could activate it for internal new Firebird database by setting experimental features to "on". You could use the external Firebird connection. A Firebird database will be created for this connection. Have a look at your screenshot. But: Behavior is still the same as described in comment 1
Created attachment 204319 [details] A Screenshot Of The Relevant Interface (In reply to Robert Großkopf from comment #7) > You could activate it for internal new Firebird database by setting > experimental features to "on". Thanks. That works. https://bugs.documentfoundation.org/show_bug.cgi?id=78034#c0 always makes locating these preferences difficult. > But: Behavior is still the same as described in comment 1 To answer what https://bugs.documentfoundation.org/show_bug.cgi?id=149938#c5 requests: > ~~~ > Version: 25.8.3.2 (X86_64) > Build ID: 580(Build:2) > OS: Linux 6.17; UI render: default; VCL: kf6 (cairo+wayland) > ~~~