empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Closed] (EMPIREDB-18) DBRecord.setModified(column, isModified) doesn't set the record state back from modified to valid
Date Mon, 04 Feb 2013 14:04:13 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rainer Döbele closed EMPIREDB-18.
---------------------------------


Cleanup of unclosed issues.
                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message