|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Well as users usually do, you are thinking of your use case. And that's fine. But that's not the only use case. As I have stated couple of times now on this issue and related ones, there are cases where users want actual literals rendered into the SQL/JDBC. In your suggestion, given that all criteria literals would be rendered as parameters, they would not be able to render to literals in SQL/JDBC at all. That's not acceptable.
But your use cases are exactly why I said I would like to allow an SF/EMF config variable.
And btw, what you suggest is certain verbose, but verbose != messy. Being explicit is never messy imho.