You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Fox (JIRA)" <ji...@apache.org> on 2014/10/26 09:20:33 UTC
[jira] [Updated] (TORQUE-332) Criteria.addJoin(String, String,
Criterion, JoinType) does not honor default schema
[ https://issues.apache.org/jira/browse/TORQUE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Fox updated TORQUE-332:
------------------------------
Summary: Criteria.addJoin(String, String, Criterion, JoinType) does not honor default schema (was: Criteria.addJoin(String, String, Criteria) does not honor default schema)
> Criteria.addJoin(String, String, Criterion, JoinType) does not honor default schema
> -----------------------------------------------------------------------------------
>
> Key: TORQUE-332
> URL: https://issues.apache.org/jira/browse/TORQUE-332
> Project: Torque
> Issue Type: Bug
> Components: Runtime
> Affects Versions: 4.0
> Reporter: Thomas Fox
> Assignee: Thomas Fox
> Fix For: 4.1
>
>
> Situation: A Default schema is set in Torque, i.e. all Table names should be prefixed with a schema name.
> A Criteria is created, using the Criteria.addJoin(String, String, Criteria), where at least one of the Strings is an unqualified table name.
> Current behaviour: The unqualified table names are retained in the SQL created from the criteria.
> Desired behaviour: The unqualified table names should be prefixed with the schema prefix
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org