https://bugs.freedesktop.org/show_bug.cgi?id=82757

          Priority: medium
            Bug ID: 82757
          Assignee: [email protected]
           Summary: Commit of unchanged date field corrupts the field
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: [email protected]
          Hardware: x86-64 (AMD64)
            Status: UNCONFIRMED
           Version: 4.4.0.0.alpha0+ Master
         Component: Database
           Product: LibreOffice

Created attachment 104807
  --> https://bugs.freedesktop.org/attachment.cgi?id=104807&action=edit
Test Database

I was testing Version: 4.3.2.0.0+
Build ID: 2087b54aab25ddbab5128af9f777b1686bc0ce5e
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-3, Time:
2014-08-17_03:55:33 

This was to check that the problem I had in #82151 has been fixed.  It has.  

However, another issue has arisen.  The attached self-contained DB demonstrates
it.

I have a table with a creation date and update count in it.  I set the creation
date on the 1st update/insert and then not again.  The update count gets set
for the 1st update and then incremented.  This is done by a form macro in a
'before record action'.

The attached database has the table and a form in it plus one macro (loosely
based on the system which has the problem).  Open the form.  Enter something in
the info column and save or tab to the next row.  All is well.

Now modify the info column in the row just entered.  The date changes (and is
sometimes invalid), even though the code has not changed it.

Now I can fix this in my code (and have in my main system so as to get on with
what I was doing), by not committing the creation date field if I haven't
changed it.

However, this is a change from 4.3.0.4, and it can't be right that any field
gets corrupted in this way by committing it unchanged.

If I've not been clear please let me know.  I've been chasing this issue for
many hours and it was really hard to find in my main system since the similar
code I use there for the whole of my system has been unchanged for a long time
and is somewhat hidden and automatic.  The problem manifested itself by
producing an invalid date, but it didn't say which table or which field was at
fault.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to