[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2576) Allow native-sql to have placeholders for default schema and catalog
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2576?page=c...
]
Steve Ebersole commented on HHH-2576:
-------------------------------------
I would like to chime in about something else I plan on adding because it impacts here.
Eventually I'd like to be able to allow native-sql queries to use the function
registry. Also I'd like to see an explicit alias notation.
The reason I bring these up is that they all use {} as delimiters. We need to consider
adding some form of distinction to these so that we know what is being referenced. For
example, for functions I had considered {fn: } as distinct delimiter; so
{fn:current_timestamp} for example.
Paul, I really like everything else you planned.
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
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira