I created a table in Design View with the following attributes:- ID Integer AutoValue YES GroupName Text 100 NOT NULL After saving the table, the attributes appeared to be still as originally set. However, after closing and then re-opening the table in design view (simply to check the settings) AutoValue had been re-set to NO. I first discovered this problem when creating a similar table for the first time and having data-entry fail because I had not inserted a value in the ID field. I should not have needed to do this as I had specified AutoValue YES. This problem has been reproduced on my Linux Mint PC and on my Windows 10 PC. LibreOffice data:- Version: 5.2.3.3 Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf CPU Threads: 2; OS Version: Linux 4.4; UI Render: default; Locale: en-GB (en_GB.UTF-8); Calc: group
Couldn't confirm this buggy behavior. Tested with Version: 5.2.4.2 Build-ID: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 CPU-Threads: 4; BS-Version: Linux 4.1; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group OpenSUSE 42.1 64bit rpm Linux, internal HSQLDB
Could you attach an example database for quick testing? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the db.
Created attachment 130176 [details] Sample database exhibiting this behaviour Sample database attached as requested.
I set the ID to have Autovalue: Yes in TestTable1. Save & reload, it was still Yes. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: bfa5bdf415fb9765139cc4d1eb040132ee484946 CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on January 5th 2016
DUPLICATE of bug 42905 ?
In that bug, it was the wizard that was misbehaving, however, here the original reporter states that they were in Design View.
MrKing : did you set the ID field as the primary key at the same time as you set the AUTOVALUE=YES option ?
(In reply to Alex Thurgood from comment #7) > MrKing : did you set the ID field as the primary key at the same time as you > set the AUTOVALUE=YES option ? Hi. No, the primary key symbol appeared automatically when I specified AutoValue YES.
(In reply to Buovjaga from comment #4) > I set the ID to have Autovalue: Yes in TestTable1. Save & reload, it was > still Yes. > > Arch Linux 64-bit, KDE Plasma 5 > Version: 5.4.0.0.alpha0+ > Build ID: bfa5bdf415fb9765139cc4d1eb040132ee484946 > CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; > Locale: fi-FI (fi_FI.UTF-8); Calc: group > Built on January 5th 2016 Hi. Interesting. I cannot even edit the table because all the properties are greyed out when I go to Design View on that table.
No repro with Version: 5.4.0.0.alpha0+ Build ID: b66b1e896c177df3c5de5d33037416152fc8a381 CPU Threads: 2; OS Version: Mac OS X 10.12.2; UI Render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group 1) Opened sample ODB file provided by reporter in comment 3 2) Created a new table Mytst 3) ID INT autovalue = YES 4) gname VARCHAR(100) NOT NULL 5) Save table 6) Attempt to close table - a question is asked whether the table should be saved again before closing - this is because the primary key is silently assigned to the ID field and that change needs to be saved - click on Yes to save and quit table. 7) Re-open table in Table design mode - autovalue is still set.
(In reply to Alex Thurgood from comment #10) > No repro with > > Version: 5.4.0.0.alpha0+ > Build ID: b66b1e896c177df3c5de5d33037416152fc8a381 > CPU Threads: 2; OS Version: Mac OS X 10.12.2; UI Render: default; > Locale: fr-FR (fr_FR.UTF-8); Calc: group > > 1) Opened sample ODB file provided by reporter in comment 3 > 2) Created a new table Mytst > 3) ID INT autovalue = YES > 4) gname VARCHAR(100) NOT NULL > 5) Save table > 6) Attempt to close table - a question is asked whether the table should be > saved again before closing - this is because the primary key is silently > assigned to the ID field and that change needs to be saved - click on Yes to > save and quit table. > 7) Re-open table in Table design mode - autovalue is still set. Hi, Thanks for that. Looks like I will have to wait for version 5.4.0.0 to be released and then the problem will be solved.
(In reply to MrKing from comment #11) > Hi, > Thanks for that. Looks like I will have to wait for version 5.4.0.0 to be > released and then the problem will be solved. You could also try with 5.3 RC http://www.libreoffice.org/download/pre-releases/ https://wiki.documentfoundation.org/Installing_in_parallel/Linux
(In reply to Buovjaga from comment #12) > (In reply to MrKing from comment #11) > > Hi, > > Thanks for that. Looks like I will have to wait for version 5.4.0.0 to be > > released and then the problem will be solved. > > You could also try with 5.3 RC > http://www.libreoffice.org/download/pre-releases/ > https://wiki.documentfoundation.org/Installing_in_parallel/Linux Hi. Thanks for the advice. Mixed results. 1) Problem solved under Windows 10 by updating JAVA and JRE. 2) No luck under Linux Mint 18.1 Cinnamon. Tried updating JAVA and JRE but no change. Tried parallel install of 5.3 RC but it would not recognise any JRE sources, so could not test the Base component. Updated from Version 5.2.3.3 to 5.2.4.2 but problem remains. The time and effort spent so far trying to solve the problem is disproportionate to the inconvenience of having to enter the ID every time; so I'll just wait for Version 5.3 Thanks again.
Per comment 13, setting as WFM - if there is a problem with the Linux version, it seems limited to the packets provided in the Mint repositories for LinuxMint - this would not be our bug, but a distro (Ubuntu) packaging bug - not for the first time, I might add.