Invalid {h-schema} replacement in native sql queries
Description
Native-sql placeholders for default schema and catalog i.e. {h-schema} replacement implemented in have bug.
It doesn't replace {h-schema} in stored procedures calls due to embed brackets i.e. "{ ? = call {h-schema}manager.check(:userId)}" do NOT get replaced correctly.
I am facing similar issue and have raised a ticket for the same. please review ticket and suggest appropriate solution/modifications.
PhilippeSeptember 25, 2015 at 2:05 PM
Hi,
This is still not working in the 4.3.7 version.
You can try it with a simple @SQLInsert annotation on the entity without precising the schema.
Can you fix it ?
Thx
Brett MeyerJuly 8, 2014 at 3:10 PM
Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!
If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.
Thank you!
qianlong morelDecember 16, 2013 at 1:54 PM
Workaround for spring is just a temporary solution. I hope this bug can be resolve soon! vote for it!!
Native-sql placeholders for default schema and catalog i.e. {h-schema} replacement implemented in have bug.
It doesn't replace {h-schema} in stored procedures calls due to embed brackets i.e. "{ ? = call {h-schema}manager.check(:userId)}" do NOT get replaced correctly.