db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fox (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TORQUE-167) Remove the field Criteria.Criterion.db
Date Fri, 15 Jul 2011 19:18:00 GMT

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

Thomas Fox resolved TORQUE-167.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0

> Remove the field Criteria.Criterion.db
> --------------------------------------
>
>                 Key: TORQUE-167
>                 URL: https://issues.apache.org/jira/browse/TORQUE-167
>             Project: Torque
>          Issue Type: Improvement
>          Components: Runtime
>            Reporter: Thomas Fox
>            Assignee: Thomas Fox
>             Fix For: 4.0
>
>
> The db field of the Criterion specifies which database dialect is used for rendering
this Criterion in SQL.
> In my opinion the database dialect should be determined from a criteria field, not from
any nested object.
> Implications:
> As a criterion is no standalone class, but an inner class of a Criteria, it always has
a criteria attached and its SQL is only rendered in the context of this criteria. As the criteria
has a field dbName by which the db adapter can be found out via Torque.getDB(criteria.getDbName()),
I propose to remove the db field from Criterion together with its getters and setters and
use the dbName field of the criteria instead to determine which Adapter should be used.

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


Mime
View raw message