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] Resolved: (EMPIREDB-33) BeanRecordProxy isFieldReadOnly wrong for new records
Date Thu, 08 Jan 2009 10:18:59 GMT

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

Rainer Döbele resolved EMPIREDB-33.
-----------------------------------

    Resolution: Fixed

Special new record behaviour has been added

> BeanRecordProxy isFieldReadOnly wrong for new records
> -----------------------------------------------------
>
>                 Key: EMPIREDB-33
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-33
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: empire-db-2.0.5-incubating
>            Reporter: Rainer Döbele
>            Priority: Minor
>             Fix For: empire-db-2.0.5-incubating
>
>
> BeanRecordProxy isFieldReadOnly always returns false for a primary key column.
> However for new records this is not desireable.
> Add special new Record behaviour.

-- 
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