empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Reiher (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] Created: (EMPIREDB-18) DBRecord.setModified(column, isModified) doesn't set the record state back from modified to valid
Date Fri, 26 Sep 2008 10:59:44 GMT
DBRecord.setModified(column, isModified) doesn't set the record state back from modified to
valid
-------------------------------------------------------------------------------------------------

                 Key: EMPIREDB-18
                 URL: https://issues.apache.org/jira/browse/EMPIREDB-18
             Project: Empire-DB
          Issue Type: Bug
          Components: Core
    Affects Versions: empire-db-2.0.4-incubating
            Reporter: Jörg Reiher
            Priority: Minor
             Fix For: empire-db-2.0.5-incubating


If you change the modified state of a record's column to "false", and by this change no column
has the modified state "true" anymore, the record state should be set back from modified to
valid.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message