[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...
]
Paul Benedict commented on HHH-2576:
------------------------------------
As you probably already know, JDBC uses {} for escape sequences, and fn is already in use
(without the colon). My references are:
* http://download.oracle.com/docs/cd/E13222_01/wls/docs91/jdbc_drivers/sqle...
* http://java.sun.com/developer/onlineTraining/Programming/JDCBook/jdbc.html
Can you entertain using the colon as protocol separator (like JDBC)? The first part would
always begin with "hibernate:" as such:
SELECT * FROM {hibernate:property:hibernate.default_schema}.table WHERE col =
{hibernate:fn:current_timestamp}
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