[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0267 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #17 from Robert Großkopf --- Still the same in LO 7.2.3.2 on OpenSUSE 15.2 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #16 from QA Administrators --- Dear Robert Großkopf, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #15 from Robert Großkopf --- Bug is the same in LO 6.3.3.2 on OpenSUSE 15.1 64bit rpm Linux -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #14 from QA Administrators --- Dear Robert Großkopf, 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 http://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 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||108445 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108445 [Bug 108445] [META] Database import/open bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Julien Nabet changed: What|Removed |Added CC|serval2...@yahoo.fr | --- Comment #13 from Julien Nabet --- I already tried to understand the code part and got completely lost, uncc myself. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Alex Thurgood changed: What|Removed |Added Priority|high|medium Severity|major |normal --- Comment #12 from Alex Thurgood --- Lowering priority, unless someone can indicate that this used to work better in an earlier version of LO. Tested against Version: 5.2.5.1 Build ID: 0312e1a284a7d50ca85a365c316c7abbf20a4d22 Threads CPU : 4; Version de l'OS :Mac OS X 10.14.1; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Alex Thurgood changed: What|Removed |Added Keywords|bibisectRequest, regression | --- Comment #11 from Alex Thurgood --- Removing bibsect and regression keywords as the AUTOVALUE keyword isn't set automatically when attempting the import into an embedded hsqldb, however, the PK is created and my test Calc data imported. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #10 from Alex Thurgood --- (In reply to Drew Jensen from comment #7) > > The first iteration of the Import Wizard when it came to physically > importing the data would display an error box should a row fail to import, > offering the user the two options; skip this record (with no explanation to > why it failed) and continue or quit the import process completely. So, this error message, instead of being improved to point out the failed insert record, was simply "removed" in a subsequent iteration of the wizard ? I feel that to be a regression in, and of, itself. > Did we do them any favors in this scenario? Almost certainly not, and therein lies the conundrum. Whichever solution gets decided though, it must work properly - currently, none of the suggested automagic implementations work, or have I misunderstood. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #9 from rob...@familiegrosskopf.de --- (In reply to Drew Jensen from comment #7) > > Some of these imports will fail for different reasons, with any unique > indexes created before the data is brought in the first time that number is > going to go up. The user didn't see why the insert of the row failed and > maybe they just gave up completely (not knowing not to use AUTOVALUE or set > a PK checkbox for this data) or maybe they sat and said toss out the row and > keep going. If there is a user who found where to create a primary key in the import-wizard (it is hidden in the contextmenu of the fields) he will know what he is doing when creating this. And only the combination of primary key and Integer should allow AutoValue to appear at this point. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #8 from Drew Jensen --- (In reply to Drew Jensen from comment #7) > (In reply to Alex Thurgood from comment #3) > > I can confirm this with > > > > Version: 6.1.2.1 > > Build ID: 65905a128db06ba48db947242809d14d3f9a93fe > > Threads CPU : 8; OS : Mac OS X 10.14; UI Render : par défaut; > > Locale : fr-FR (fr_FR.UTF-8); Calc: group threaded > > In the Import Wizard (used to bring row data from an external source into a > Base table) though this inability to set a PK with an existing column was > IIRC a decision not an accident. > > The ability is included, as you mention, to create an additional field for > an IDENTITY column in the target database table if the table is being > created during the current import session. > > So why not include the ability to use a column of data from the source data? > > That discussion was now 14+ years behind us - // insert quote on aging > so with human memory failings something along the lines of iirc > > The import functionality was to begin with a limited amount of data > validation/manipulation capabilities. (I don't see where that has changed to > a significant degree) > > That a user may be dropping a collection of rows onto the application from > any number of applications/sources and the wizard should target the most > basic office software user. > > The first iteration of the Import Wizard when it came to physically > importing the data would display an error box should a row fail to import, > offering the user the two options; skip this record (with no explanation to > why it failed) and continue or quit the import process completely. > > OK - so lets look at an office software user who found some tabular data on > a website and copy a block of it. They paste that into Base and start the > Import Wizard. So they read a couple of articles, browsed a manual and > watched a video, they know it is good to have a primary key and they go > about using what looks like a good candidate in that data. > > Some of these imports will fail for different reasons, with any unique > indexes created before the data is brought in the first time that number is > going to go up. The user didn't see why the insert of the row failed and > maybe they just gave up completely (not knowing not to use AUTOVALUE or set > a PK checkbox for this data) or maybe they sat and said toss out the row and > keep going. > > Did we do them any favors in this scenario? My answer to that question is no, the best thing we could do for that scenario and the user was to nudge them to add an additional column for use as a PK in the new table and maximize the chances of bringing in all the rows of data they attempted to import. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #7 from Drew Jensen --- (In reply to Alex Thurgood from comment #3) > I can confirm this with > > Version: 6.1.2.1 > Build ID: 65905a128db06ba48db947242809d14d3f9a93fe > Threads CPU : 8; OS : Mac OS X 10.14; UI Render : par défaut; > Locale : fr-FR (fr_FR.UTF-8); Calc: group threaded In the Import Wizard (used to bring row data from an external source into a Base table) though this inability to set a PK with an existing column was IIRC a decision not an accident. The ability is included, as you mention, to create an additional field for an IDENTITY column in the target database table if the table is being created during the current import session. So why not include the ability to use a column of data from the source data? That discussion was now 14+ years behind us - // insert quote on aging so with human memory failings something along the lines of iirc The import functionality was to begin with a limited amount of data validation/manipulation capabilities. (I don't see where that has changed to a significant degree) That a user may be dropping a collection of rows onto the application from any number of applications/sources and the wizard should target the most basic office software user. The first iteration of the Import Wizard when it came to physically importing the data would display an error box should a row fail to import, offering the user the two options; skip this record (with no explanation to why it failed) and continue or quit the import process completely. OK - so lets look at an office software user who found some tabular data on a website and copy a block of it. They paste that into Base and start the Import Wizard. So they read a couple of articles, browsed a manual and watched a video, they know it is good to have a primary key and they go about using what looks like a good candidate in that data. Some of these imports will fail for different reasons, with any unique indexes created before the data is brought in the first time that number is going to go up. The user didn't see why the insert of the row failed and maybe they just gave up completely (not knowing not to use AUTOVALUE or set a PK checkbox for this data) or maybe they sat and said toss out the row and keep going. Did we do them any favors in this scenario? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #6 from Drew Jensen --- (In reply to Alex Thurgood from comment #5) > Possible DUP of bug 117527 This is why I changed the summary. Table Wizard in Base to most of us refers to 'Create new Table Wizard' started from within the Base UI. This issue is about the Import Wizard wich starts when the user drops (or pastes) row based data onto the Base UI. Those two 'wizards' are TTBOMK different beasts in the code base and yes there are issues with PK creation in the Base 'New Table Wizard' also. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #5 from Alex Thurgood --- Possible DUP of bug 117527 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Alex Thurgood changed: What|Removed |Added Keywords||bibisectRequest, regression Severity|normal |major Priority|medium |high -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Alex Thurgood changed: What|Removed |Added Version|6.1.3.2 release |6.1.2.1 release -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #4 from Alex Thurgood --- I tested on a Firebird ODB database, so perhaps this is not representative given the already huge problems that this currently has, however, I was unable to either produce a PK using the GUI autovalue, or alternatively, ignoring that first wizard screen option, and waiting until the end of the table creation when the user is asked whether they would like to add a PK field. In both cases, i.e manual definition in first wizard screen, or wizard executed suggestion, the PK field could not be created. I seem to have seen this issue already reported though, so this current report might be a DUP. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Alex Thurgood changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Alex Thurgood --- I can confirm this with Version: 6.1.2.1 Build ID: 65905a128db06ba48db947242809d14d3f9a93fe Threads CPU : 8; OS : Mac OS X 10.14; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 --- Comment #2 from rob...@familiegrosskopf.de --- (In reply to Drew Jensen from comment #1) > Setting the field to Integer(Autovalue) which becomes an IDENTITY would also > automatically create that PK. > > In the case of importing from a Calc this could lead rows with duplicate > values in the Calc column not importing. If you could create a primarykey for a field you couldn't import a Calc-table with duplicate values. This is independent of AutoValue "yes" or "no". The import would fail. So the bug is: primarykey could be created and AutoValue could not. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range
https://bugs.documentfoundation.org/show_bug.cgi?id=121210 Drew Jensen changed: What|Removed |Added Summary|TABLEWIZARD: No possibility |IMPORT: No possibility to |to set Auto Value to a |set Auto Value to a Integer |Integer Primary Key |Primary Key when importing ||Calc range --- Comment #1 from Drew Jensen --- Setting the field to Integer(Autovalue) which becomes an IDENTITY would also automatically create that PK. In the case of importing from a Calc this could lead rows with duplicate values in the Calc column not importing. Is this a better solution than importing all the rows? With all the rows in the database then if the user adds a PK for that column of data the step of doing so will give an error should a duplicate arise, offering the user the chance to fixup the value as needed. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
