Difference: UnicodeSETStmt (12 vs. 13)

Revision 132011-04-15 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

SET Statement

Line: 68 to 68
 
  1. Does not throw transcode error when moving raw to National when raw contains non national data
  2. A Raw alpha containing \u#### or \U######## does not get transcoded to Unicode.
  3. SETing a unicode character into a raw alpha generates a 'Value Does Not Fit In Mask' runtime error. It should be transcode error.
Changed:
<
<
  1. SETing a national character into a raw alpha generates a 'Value Does Not Fit In Mask' runtime error. It should be transcode error.
>
>
  1. SETing a national character into a raw alpha generates a 'Value Does Not Fit In Mask' runtime error. Should not be an error at all, should it? Raw should accept any 8 bit value, right?
 
  1. SETing a Unicode Character into a National field, where the Unicode character is not part of the National set does not create a transcode error.
Changed:
<
<
>
>
  1. SET statement gives runtime error 'Value Does Not Fit in Mask' when attempting to move unicode field containing \u00A4 into it. I thought any 8 bit character was valid for Raw fields?
  -- SteveFrizzell - 2011-03-07 \ No newline at end of file
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback