empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddhartha Upadhyaya (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] [Created] (EMPIREDB-200) Option to have non-persistent column in DBTable / DBView
Date Sat, 23 Nov 2013 19:01:35 GMT
Siddhartha Upadhyaya created EMPIREDB-200:
---------------------------------------------

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


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
(v6.1#6144)

Mime
View raw message