[
https://issues.apache.org/jira/browse/OPENJPA-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-1724:
----------------------------------
Attachment: OPENJPA-1724.diff
New "-sqlEncode" or "-se" flag for MappingTool, which allows the user to
specify a Java charset to use (like UTF-8), instead of the current JVM locale.
Added new mapping sample under openjpa-examples which shows how to use
MappingTool from an ANT task, along with two entities which one has normal
ASCII characters and the other has Unicode escaped character to show the output
differences when "-sqlEncode UTF-8" is used.
> Allow MappingTool to generate DDL SQL files in a different encoding than the
> local JVM
> --------------------------------------------------------------------------------------
>
> Key: OPENJPA-1724
> URL: https://issues.apache.org/jira/browse/OPENJPA-1724
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc, tooling
> Affects Versions: 1.2.2, 1.3.0, 2.0.0
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.1.0
>
> Attachments: OPENJPA-1724.diff
>
>
> Handle case where Java code is using UTF-8 encoded characters and we want the
> output DDL files to remain in UTF-8, instead of default to unicode UTF-16.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
