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] [Commented] (EMPIREDB-159) The setBeanValues method in DBRecord and Timestamp
Date Mon, 04 Feb 2013 13:18:12 GMT

    [ https://issues.apache.org/jira/browse/EMPIREDB-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570153#comment-13570153

Rainer Döbele commented on EMPIREDB-159:

Hi Dimitar,

there is an overload of that method that allows you to specify which fields (or columns repectively)
to ingore.

Also you can override the setBeanValues in DBRecord yourself and implement specific logic.

Further als Franics has noted, all readOnly columns will already be ingored.

Still demand for a change?
If so, please give us more specific information why?

Otherwise we are going to close this issue.


> The setBeanValues method in DBRecord and Timestamp
> --------------------------------------------------
>                 Key: EMPIREDB-159
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-159
>             Project: Empire-DB
>          Issue Type: Improvement
>         Environment: JDK 6
>            Reporter: Dimitar Simeonov
>              Labels: DBRecord, Timestamp,
> The method should skip/ignore timestamp column(s). 

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

View raw message