[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_30953 ]

Thomas Masutti commented on HHH-2576:
-------------------------------------

The workaround is to use an Interceptor and replace the placeholder.

> Allow native-sql to have placeholders for default schema and catalog
> --------------------------------------------------------------------
>
>           Key: HHH-2576
>           URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2576
>         Project: Hibernate3
>       Issue Type: Improvement
>       Components: query-sql
>   Affects Versions: 3.2.3
>        Reporter: Max Rydahl Andersen
>
> we shold consider allowing something like:
> <sql-query name="queryName" callable="true">
> { call ${default_schema}.storedProcName() }
> </sql-query>
> similar for normal SQL queries too.
> <sql-query name="queryName">
> select * from ${default_schema}.CUSTOMER x where ...
> </sql-query>
> Maybe ${catalogschema} should be allowed to which would be the full prefix needed dependent on the dialect and would free one from having both catalog and schema + poper seperators in there.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

   
_______________________________________________
hibernate-issues mailing list
hibernate-issues@(protected)
https://lists.jboss.org/mailman/listinfo/hibernate-issues