You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2018/10/19 10:45:00 UTC

[jira] [Closed] (EMPIREDB-200) Option to have non-persistent column in DBTable / DBView

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

Rainer Döbele closed EMPIREDB-200.
----------------------------------
    Resolution: Won't Fix

cannot be implemented.

> Option to have non-persistent column in DBTable / DBView
> --------------------------------------------------------
>
>                 Key: EMPIREDB-200
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-200
>             Project: Empire-DB
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: empire-db-2.4.2
>            Reporter: Siddhartha Upadhyaya
>            Priority: Major
>
> Option to have non-persistent column in DBTable / DBView.
> We should have option to add a column / attribute for DBTable / DBView, which is non-persistent in nature. So, the value of the Column / attribute will not be stored in the Database, but it will be available as part of the Java Object to the application. The value of the column / attribute will be depend on the business logic.
> If we consider DBRecord is the Java Bean in an business layer. we may need to store some of the calculated data. This option will have us to do it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)