[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2576) Allow native-sql to have placeholders for default schema and catalog

[Paul Benedict (JIRA)]

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

Paul Benedict commented on HHH-2576:
------------------------------------

Yes, I am of the same thought that {hibernate-fn} is way too verbose. I will run with {h-fn/prop} until it is decided to be too concise :-) 

As for needing "unrestricted access to all properties", my answer is maybe. As the first patch shows, only schema and catalog have explicit handling currently, but I see great potential if any property was accessible. Even if hibernate.xxx are not the most interesting properties, opening the door for developers to incorporate application specific properties seem pretty useful.

How about this:
1) {h-schema} and {h-schema.} for unqualified and qualified schema replacement
2) {h-catalog} for catalog replacement (do we need qualified access?)
3) {h-prop xxx} for a property
4) {h-fn xxx} for a function

> 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: Hibernate Core
>          Issue Type: Improvement
>          Components: query-sql
>    Affects Versions: 3.2.3
>            Reporter: Max Rydahl Andersen
>         Attachments: HHH-2576-01.patch
>
>
> 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