[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-2576) Allow native-sql to have placeholders for default schema and catalog
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2576?page=c...
]
Paul Benedict updated HHH-2576:
-------------------------------
Attachment: HHH-2576-R4.patch
Attached is an updated patch with {h-domain}. One thing of note, you'll see some
duplicated code to generate the catalog/schema combination, but that was intentional. I
could have refactored into a private method, but because SQL replacement should be speedy
-- and these replacements are likely to appear (often) whenever a table is specified -- I
chose not to incur additional method invocations.
Steve, could you also add a Fix Version of 3.3? I would like to use it earlier in my day
job :-)
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
Assignee: Steve Ebersole
Fix For: 3.5
Attachments: HHH-2576-01.patch, HHH-2576-R2.patch, HHH-2576-R3.patch,
HHH-2576-R4.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