Mailing-List: contact commits-help@empire-db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@empire-db.apache.org
Date: Sat, 23 Nov 2013 19:01:35 +0000 (UTC)
From: "Siddhartha Upadhyaya (JIRA)" <empire-db-dev@incubator.apache.org>
To: empire-db-commits@incubator.apache.org
Message-ID: <JIRA.12680894.1385233288003.19440.1385233295122@arcas>
In-Reply-To: <JIRA.12680894.1385233288003@arcas>
References: <JIRA.12680894.1385233288003@arcas>
Subject: [jira] [Created] (EMPIREDB-200) Option to have non-persistent
 column in DBTable / DBView
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)