Description: Unable to edit data in LibreOffice Base after upgrade. Steps to Reproduce: 1.Upgrade from 6.1.5.2 to 6.2.3.2 2.Open Base odb. 3.Double-click on any table Actual Results: Edit Mode is disabled. Expected Results: The ability to insert rows or modify. Reproducible: Always User Profile Reset: No Additional Info:
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
(In reply to raal from comment #1) > Hello, > > Thank you for filing the bug. Please send us a sample document, as this > makes it easier for us to verify the bug. > I have set the bug's status to 'NEEDINFO', so please do change it back to > 'UNCONFIRMED' once you have attached a document. > (Please note that the attachment will be public, remove any sensitive > information before attaching it.) > How can I eliminate confidential data from a sample document? > https://wiki.documentfoundation.org/QA/ > FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F > Thank you Sorry but I am just too busy at the moment. This is just a very simple bug. It is not related to any specific file or table. I have downgraded to 6.1.5.2 so as to be able to continue and everything works as expected again.
To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
(In reply to Xisco Faulí from comment #3) > To be certain the reported issue is not > related to corruption in the user profile, could you please reset your > Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and > re-test? > > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the issue is still present Ok I renamed the user profile directory and it has not fixed or restored the ability to maintain my databases, ie. no editing.
@Robert : when reporting Base bugs, please provide the following minimum information : - OS type and version (distribution name and version if Linux/Unix); - bit type and version of LibreOffice; - Java JDK/JVM version - type and version of database engine configured in your ODB file ; - type and version of database driver you are using to connect to the database; - any salient details of the ODB : particular table definitions, queries, forms, reports, etc, that might have an influence From the settings you chose in bugzilla when you reported this bug, it appears that you are using a 32bit version of LibreOffice on Windows - can you confirm that you are using a 32bit version of LibreOffice on Windows ? Which version of Windows ?
(In reply to Alex Thurgood from comment #5) > @Robert : when reporting Base bugs, please provide the following minimum > information : > > - OS type and version (distribution name and version if Linux/Unix); > - bit type and version of LibreOffice; > - Java JDK/JVM version > - type and version of database engine configured in your ODB file ; > - type and version of database driver you are using to connect to the > database; > - any salient details of the ODB : particular table definitions, queries, > forms, reports, etc, that might have an influence > > From the settings you chose in bugzilla when you reported this bug, it > appears that you are using a 32bit version of LibreOffice on Windows - can > you confirm that you are using a 32bit version of LibreOffice on Windows ? > > Which version of Windows ? Yes, Windows 10 Version 1803 LibreOffice 6.2.3.2 32 bit (because 64bit doesn't support aoo-my-sdbc-1.2.0-windows-x86.oxt otherwise I get no sdbc:mysql: etc) Java 8 Update 211 MySql Server 5.6 aoo-my-sdbc-1.2.0-windows-x86.oxt none
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Robert from comment #6) > > Which version of Windows ? > > Yes, Windows 10 Version 1803 > LibreOffice 6.2.3.2 32 bit (because 64bit doesn't support > aoo-my-sdbc-1.2.0-windows-x86.oxt otherwise I get no sdbc:mysql: etc) You don't need this extension any more as mysql/mariadb-sdbc-connector is supposed to be integrated directly into the code. > aoo-my-sdbc-1.2.0-windows-x86.oxt My suggestion would be to remove LO 32bit, and try with LO64bit without the 32bit extension for aoo-my-sdbc. You might need to create a new user profile for this as the previous user-added extension and the new internal connector code can conflict with each other. Please try this and report back.
(In reply to Alex Thurgood from comment #8) > (In reply to Robert from comment #6) > > > > > Which version of Windows ? > > > > Yes, Windows 10 Version 1803 > > LibreOffice 6.2.3.2 32 bit (because 64bit doesn't support > > aoo-my-sdbc-1.2.0-windows-x86.oxt otherwise I get no sdbc:mysql: etc) > > You don't need this extension any more as mysql/mariadb-sdbc-connector is > supposed to be integrated directly into the code. > > > > aoo-my-sdbc-1.2.0-windows-x86.oxt > > > My suggestion would be to remove LO 32bit, and try with LO64bit without the > 32bit extension for aoo-my-sdbc. > > You might need to create a new user profile for this as the previous > user-added extension and the new internal connector code can conflict with > each other. > > Please try this and report back. Ok I uninstalled my previous version, renamed the user profile directory, installed version 6.2.4.2 64bit. Still not able to add rows etc. I then uninstalled 6.2.4.2, removed user profile, installed 6.1.6.3 64bit. The error as soon as I try to open table is "No SDBC driver was found for the URL 'sdbc:mysql:mysqlc:localhost:3306/rob'". So I am going back to the 32bit version which works.
(In reply to Robert from comment #9) > I then uninstalled 6.2.4.2, removed user profile, installed 6.1.6.3 64bit. > The error as soon as I try to open table is "No SDBC driver was found for > the URL 'sdbc:mysql:mysqlc:localhost:3306/rob'". > This is to be expected if you don't have the connector-extension installed, as 6.1.x required a connector extension in order to have the SDBC driver interface. It is somewhat strange however, that LO6.2.x didn't work for you without the connector extension as it is supposed to be integrated directly into this branch. Not much more I can do here, as I don't have a 64bit Win10 machine on which to test this.
Additionally, the AOO connector is not a LibreOffice extension unless mistaken, so if there is a problem with the connector extension itself, there isn't very much that will be done about it within the LO project. Other things that mitigate against finding a resolution to the bug, if such is even confirmed: - 32bit versions of LO will eventually be phased out completely in favour of 64bit LO for Win; - LO6.1.x branch will soon be end of life (May 29, 2019) ; - LO6.2.x integrates an appropriate SDBC native connector without the need for installing a separate extension.
(In reply to Alex Thurgood from comment #12) > Additionally, the AOO connector is not a LibreOffice extension unless > mistaken, so if there is a problem with the connector extension itself, > there isn't very much that will be done about it within the LO project. > > Other things that mitigate against finding a resolution to the bug, if such > is even confirmed: > > - 32bit versions of LO will eventually be phased out completely in favour of > 64bit LO for Win; > - LO6.1.x branch will soon be end of life (May 29, 2019) ; > - LO6.2.x integrates an appropriate SDBC native connector without the need > for installing a separate extension. Yes but 6.2.x does not work as I have tried to demonstrate. I don't think it is a problem with the AOO extension. I don't think it is any function of the AOO drivers to set whether or not to allow database updates, that's something else. Surely there is some logging I could turn on to see the interaction with the DB server. Maybe the DB is returning read-only for example, unlikely I think. I am using MySQL version 5.6.21.
Possibly a DUP of bug 122446 ?
(In reply to Alex Thurgood from comment #14) > Possibly a DUP of bug 122446 ? Yes the same. Does this mean I will have to wait for 6.3 to get a fix?
*** This bug has been marked as a duplicate of bug 122446 ***
(In reply to Robert from comment #15) > Does this mean I will have to wait for 6.3 to get a fix? Looks like it.
(In reply to Alex Thurgood from comment #17) > (In reply to Robert from comment #15) > > > > Does this mean I will have to wait for 6.3 to get a fix? > > Looks like it. Just to add. I have now had the time to try this on Linux. Mint 18.3 Linux 4.15.0-50-generic mySQL 5.7.26 LibreOffice 6.2.4.2 And guess what? I get the exact same problem with not being able to add rows. I had previously version 6.1 and 1.2 of the oo drivers which worked. I did a apt-get -purge libre etc before installing version 6.2.4.2. I then removed the oo extension via the ext manager.