[ http://issues.apache.org/jira/browse/DERBY-164?page=all ]
Jean T. Anderson resolved DERBY-164:
------------------------------------
Resolution: Fixed
Fix Version: 10.1.0.0
Patch committed revision 169667.
> unicodeEscape command in ij doesn't work
> ----------------------------------------
>
> Key: DERBY-164
> URL: http://issues.apache.org/jira/browse/DERBY-164
> Project: Derby
> Type: Bug
> Components: Documentation, Localization
> Versions: 10.0.2.1
> Environment: Java Version: 1.4.2_03
> Java Vendor: Sun Microsystems Inc.
> OS name: Windows XP
> OS architecture: x86
> OS version: 5.1
> Reporter: Ramon Liu
> Fix For: 10.1.0.0
> Attachments: derby164.diff
>
> According to the document about ij:
> Use unicodeEscape command during an ij session to allow unicode escape
> sequences as input characters during the ij session. By default,
> unicodeEscape is set to 'off' (ij does not accept unicode escape characters).
> ij> unicodeescape on;
> ij> VALUES '\u00f1';
> 1
> -
> �
> ij> unicodeescape off;
> ij> VALUES '\u00f1';
> 1
> ------
> \u00f1
> BUT, now, this command doesn't work. Neither unicodeescape is set to on nor
> off, '\u00f1' is displayed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
