Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Date: Wed, 3 Aug 2011 15:16:27 +0000 (UTC)
From: "CG Monroe (JIRA)" <jira@apache.org>
To: torque-dev@db.apache.org
Message-ID: 
 <920331845.4905.1312384587317.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (TORQUE-147) Database objects should not need to
 inherit from BaseObject
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/TORQUE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078792#comment-13078792 ] 

CG Monroe commented on TORQUE-147:
----------------------------------

(Sorry for the direct torque-dev response.. re-doing it for the Jira issue).

Moving methods to generated / changing interface +1 from me.

Get/SetByName, et. al.

IMHO, it would be *NICE* to have an interface that covers these.  A use case for this would be common normalization or lookup functions.  E.g., a function with a record object and column name as parameters that does something common to multiple table and columns, like scanning for profanity or normalizing case in across multiple tables that contains title and description fields.

Perhaps this could be based on the java LinkedHashMap object methods or the org.apache.commons.collections.OrderedMap interface?  With the key being the column name.  Then allow users the choice of simple persistent objects or collection based persistent objects (which is a superset of the simple objects).

I think you're right about getTableMap. That is Torque specific (but needed).  If someone needs it inside a function using an interface parameter, they can always use the baseObject or cast   


> Database objects should not need to inherit from BaseObject
> -----------------------------------------------------------
>
>                 Key: TORQUE-147
>                 URL: https://issues.apache.org/jira/browse/TORQUE-147
>             Project: Torque
>          Issue Type: Improvement
>            Reporter: Thomas Fox
>            Assignee: Thomas Fox
>             Fix For: 4.0
>
>
> Currently it is an error if database objects do not inherit from BaseObject. This makes embedding of Torque objects in other frameworks very difficult, because it does not allow to choose an own parent to inherit from.
> The minimum requirement would be that it is not required any more that database objects inherit from BaseObject.
> Ideally BaseObject dies and the base objects inherit directly from java.lang.object.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org