[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2576?page=c...
]
Steve Ebersole commented on HHH-2576:
-------------------------------------
Yes I am aware of the JDBC escape syntax.
As for keeping references to the properties, the main argument against keeping them is
that it would send the wrong implication wrt changing the values.
I first started considering this whole idea in regards to mapping fragments, specifically
in <formula/> mappings.
I'm fine to entertain other delimiters. I just went with {fn: } for (1) succinctness,
(2) naturalness and (3) familiarity.
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira