[
https://issues.apache.org/jira/browse/OPENJPA-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142045#comment-18142045
]
ASF subversion and git services commented on OPENJPA-3070:
----------------------------------------------------------
Commit f782de500c9d2e67528d2f9418aa36d074edcd2d in openjpa's branch
refs/heads/OPENJPA-2935 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=f782de500 ]
[OPENJPA-3070] Write string values into SQL text so that they reach the
database unchanged
Values written as literals (CASE, COALESCE, NULLIF, and with the
UseLiteralInSQL hint) now have their quotes doubled. Values with a
backslash on MySQL, MariaDB and PostgreSQL, and values with non-ASCII
characters on SQL Server and Sybase, are bound as parameters instead.
> String values written as SQL literals do not always reach the database
> unchanged
> --------------------------------------------------------------------------------
>
> Key: OPENJPA-3070
> URL: https://issues.apache.org/jira/browse/OPENJPA-3070
> Project: OpenJPA
> Issue Type: Bug
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
> Fix For: 4.2.0
>
>
> String values that are written into the SQL text (CASE, COALESCE and NULLIF
> values, and all literals with the openjpa.hint.UseLiteralInSQL hint) can be
> read differently by the database when they contain a quote or a backslash,
> for example on MySQL and MariaDB.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
