[hibernate-issues] [Hibernate-JIRA] Updated: (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:all-tabpanel ]

Paul Benedict updated HHH-2576:
-------------------------------

    Attachment: HHH-2576-01.patch

Attached is my first patch for this issue. I tested against 3.3.x just fine.

* Unlike previously stated, not all Hibernate properties are available (only hibernate.default_schema and hibernate.default_catalog) and that is because session factories do not keep a reference to their configuration properties. This limitation is explicitly stated in o.h.cfg.Environment, but perhaps the design decision should be rethought? If it proves a good idea to expose any property in SQL (and perhaps HQL too?), then I think the limitation should definitely be lifted.

* Steve, thanks for making me aware of SQLFunctionRegistry. I see its association in SessionFactoryImplementor. Can you please explain how you would want to integrate it? If we can, as you said, come up with a unified substitution notation for hibernate-specific values, I can attempt to integrate the two.

> 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