Created attachment 133959 [details] Sample database file The Summary/title line above says it all. To demonstrate this feature open the form in the attachment. Click on the 4th line in either table control to start a new record. Note that defaults are working for all but the Date/time (Time) field which gets 0:00 rather than the set default. Contrast this with the fact that defaults do work properly for Time, Date, and Date/Time (Date) type fields. In addition all of these work properly in Tables and Queries. It's only Form, Table control, Date/Time (time) fields that don't work properly. I have tested this both with the embedded HSQLDB 1.8 and with a connected MariaDB 10.1. The attachment here only uses the embedded HSQLDB database. Associated issues: I think there are also other related issues with the inability to easily enter dates and times in Table Controls, and will submit as separate issues. But I note this here because at the same time as someone is working on this they might also want to fix some other related issues. Note that if you create a table control using the wizard, using an underlying data source with a Date/Time type field, the wizard will create two Table Control columns: a Date/time (Date) and a Date/time (Time). It's the 2nd of these that is not working properly. Debian Jessie 8.8-64 w/ cinnamon 2.2.16. Thanks.
Reproduced with file. Did you also test with Firebird? Win 7 Pro 64-bit Version: 5.4.0.0.alpha1+ (x64) Build ID: d02d52887678cd3d518c19a235bc443c292b3041 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2017-05-01_22:53:14 Locale: fi-FI (fi_FI); Calc: CL
Created attachment 134000 [details] Firebird error message
(In reply to Buovjaga from comment #1) > Reproduced with file. > > Did you also test with Firebird? I just tested w/ Firebird. Yes this also happens w/ Firebird, but w/ different error message: "Error updating the current record firebird_sdbc error: *value exceeds the range for valid timestamps caused by 'isc dsql execute'"
Created attachment 134001 [details] Sample database using firebird
On pc Debian x86-64 with master sources updated yesterday, I could reproduce this. Just for my information, where do you put default time, date or other? In table design, default values are empty and I don't find other places.
Thought this was a regression, but having tested against Version: 4.4.5.2 Build ID: a22f674fd25a3b6f45bdebf25400ed2adff0ff99 Locale : fr_FR.UTF-8 macOS 10.14.2 it seems like this was the beahviour at least back to that version. Testing earlier versions of LO is complicated on macOS because it requires the presence of the JavaforOSX package which is deprecated.
I can also reproduce this in Version: 4.2.5.2 Build ID: 61cb170a04bb1f12e77c884eab9192be736ec5f5
I gave it a try with master sources updated yesterday. 1) Firebird file shows no table for me even if I enable advanced features and no message on console to indicate why. 2) I could reproduce this with hsqldb but and had different messages on console: warn:tools.datetime:6904:6904:tools/source/datetime/tdate.cxx:102: Date::setDateFromDMY - sure about 0 year? It's not in the calendar warn:legacy.osl:6072:6072:svx/source/fmcomp/gridctrl.cxx:2120: DbGridControl::SetCurrent : SeekRow failed ! warn:legacy.osl:6072:6072:svtools/source/brwbox/brwbox3.cxx:376: Illegal call here! Between datetime format in table, datetime format in forms, the different date limits between database types, I'm lost => I can't help here, uncc myself
Dear Howard Johnson, 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://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
I think these 'Dear xx' letters are stupid and I refuse to put more time into this until there is a real effort to fix these bugs. It would be ok to just let them hang, but these letters asking us to reconfirm again and again just rub me the wrong way.
(In reply to Howard Johnson from comment #10) > I think these 'Dear xx' letters are stupid and I refuse to put more time > into this until there is a real effort to fix these bugs. It would be ok to > just let them hang, but these letters asking us to reconfirm again and again > just rub me the wrong way. I get where you're coming from, but numerous experiments have shown that retesting after 1 year yields about 25% "silently fixed" reports (ie. might have been duplicates). It is true that for some areas that are not seeing intensive work, such as Base, it is a bit problematic to keep pinging.
(In reply to Buovjaga from comment #11) > > I get where you're coming from, but numerous experiments have shown that > retesting after 1 year yields about 25% "silently fixed" reports (ie. might > have been duplicates). It is true that for some areas that are not seeing > intensive work, such as Base, it is a bit problematic to keep pinging. It is indeed very rare for anything Base related to get fixed by "accident", or as a result of a fix somewhere else in the code.
(In reply to Howard Johnson from comment #10) > I think these 'Dear xx' letters are stupid and I refuse to put more time > into this until there is a real effort to fix these bugs. It would be ok to > just let them hang, but these letters asking us to reconfirm again and again > just rub me the wrong way. I argued this very point many years ago when the "bug the original bug reporter" email idea was first floated, but then I'm mostly a Base/Writer user, on a 2nd class OS, where LO is concerned ;-) You can still have my +1 though.
Dear Howard Johnson, 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
Have tested this one. Seems to be a little tricky but got it working. Only time in a form control, which is defined as time from a TIMESTAMP field, won't work. 1. Create the table with data and datetime fields 2. Set the defaults in this table. For a date and a datetime field it will only work with YYYY-MM-DD YYYY-MM-DD HH:MM:SS If I try it with the German format, with is shown as example it didn't work. But it will show the fields formatted in German format … 3. Create a form with a separate date and time field an a formatted field for datetime. Form will show the default values for datetime in the formatted field. Only wouldn't show the right default time in the separate time field. Tsted with Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded (OpenSUSE 15.3 64bit rpm Linux)
Created attachment 184792 [details] DateTime default working in formatted field, if defined in table
Comment on attachment 134001 [details] Sample database using firebird File doesn't contain any database. Seems to contain a form, which isn't shown when opening the file.
Bug for the separate Time control for a datetime-field of the database still exists. Tested with OpenSUSE 15.3 64bit rpm Linux, LibreOffice 7.5.0.2
Confirming that bug still present also in Version: 7.6.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 7f23dae00fedc9d7119b44b6c44d9eca4f8c87b8 CPU threads: 8; OS: Mac OS X 13.0.1; UI render: Skia/Metal; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded daily build master 24/01/2023.