![]() If you want to do more to help you can test to see if your issue is a REGRESSION. Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not ![]() Reply via email (please reply directly on the bug tracker) ![]() 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. If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. Test to see if the bug is still present with the latest version of LibreOffice from If you have time, please do the following: We'd really appreciate your help in getting confirmation that the bug is still present. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. There have been thousands of bug fixes and commits since anyone checked on this bug report. 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. Whilst I agree pretty much with your suggestions, I don't really understand how that will solve the timestamp issue ? We would need both entries to be complete, especially if they are diverging. > fact the 2 DBs will have more and more difference with the time? > about renaming Mysql to MariaDB to prepare the > (When a bug talks about Mysql with JDBC, how to know if Mysql_jdbc has beenĬurrently, as far as I know, the only visual clue is in the bottom of the Base window, where it specifies the type of connection being used. If we do decide to go for just one list, then yes, bearing in mind the UI rework required. > If disagree, why don't we do the same for Postgresql for example? Personally, I'm not opposed to this, but we need to be consistent IMO. If we just had JDBC at that first step, then we would have to add specific entries in the first menu for the alternative MySQL connection possibilities. Currently, the DB creation wizard (and also the mailmerge wizard, off the top of my head, and possibly the Define Addressbook dialog) gives you a specific dialog if you choose MySQL as the intended database at the first step. I suspect that would require a rework of the UI (and the help) as well though. > why not just keeping jdbc and dump mysql_jdbc to simplify? (When a bug talks about Mysql with JDBC, how to know if Mysql_jdbc has been used or just JDBC?)Ģ) We use Mariadb package 2.0.0 (see ), what about renaming Mysql to MariaDB to prepare theįact the 2 DBs will have more and more difference with the time? If disagree, why don't we do the same for Postgresql for example? Selecting Mysql (or MariaDB if 1) is done), should just bring direct connection summarizes well the situation about JDBC with MariaDB/Mysql.Ĭom.: the legacy class used for MysqlĬom.mysql.cj.jdbc.Driver: for recent Mysqlġ) We got "mysql_jdbc" and "jdbc" drivers (see ), why not just keeping jdbc and dump mysql_jdbc to simplify? The timestamp field should be displayed in the UI and allow data entry. ANy attempt to enter data in the fname field will generate an error indicating that required data for the missing ts field has not been entered ! Notice that the timestamp field is not displayed.Ħ. Double-click on the table ts7 to open the data entry modeĥ. ![]() Refresh the list of tables in the LO UIĤ. For example, use the following DDL in the Tools > SQL dialog or via the mysql command line:Ĭreate table ts7 (id INT NOT NULL AUTO_INCREMENT PRIMARY KEY, fname VARCHAR(50), ts7 TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP) ģ. Create a mysql table containing a NOT NULL timestamp field with DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMPĢ. Setting the connection parameter string zeroDateTimeBehavior=convertToNull doesn't have any effect on the display, even after a shutdown and relaunch of LO.ġ. In comparison, using the native mysql connector extension shows the timestamp fields. Mysql timestamp fields are not displayed in table data entry mode after double-clicking on a table.
0 Comments
Leave a Reply. |