Difference: UnicodeBEG_AT_END_ATStmt (1 vs. 5)

Revision 52011-06-02 - JeanNeron

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

BEG AT / END AT Statements

Line: 28 to 28
 
  • Test literal operands with National/Unicode keys (should be error)

Bugs

Deleted:
<
<
  1. Errors not not thrown when literals are used with Unicode/National keys * Not a bug * Functions as designed.
  2. Records not read when using a group field that includes Unicode characters.
 \ No newline at end of file
Added:
>
>
  1. Errors not not thrown when literals are used with Unicode/National keys * Not a bug * Functions as designed.
  2. Records not read when using a group field that includes Unicode characters. * Fixed * Tested May 23 engine
 \ No newline at end of file

Revision 42011-05-16 - JeanNeron

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

BEG AT / END AT Statements

Line: 17 to 17
 
  • Literal operand:
    • All literal values are considered to be RAW alpha values and encoding of 8859-15.
    • Unicode escape sequences are NOT honored.
Changed:
<
<
    • Literal values CANNOT be used to specify the range of records to read when the corresponding key field is a UNICODE or NATIONAL alpha field.
>
>
    • Literal values are entered as a string of single-byte characters with an 8859-15 (RAW Alpha) encoding. The string of bytes representing the literal characters is later used as a constraint for the key specified on a corresponding BEG READ or READNEXT statement. No conversion or transcoding of a literal BEG AT/END AT value is performed regardless of the type of key field specified on the corresponding BEG READ/READNEXT statement. This means that literal values on a BEG AT/END AT statement should probably only be used when the key field on the corresponding BEG READ/READNEXT statement is a RAW alpha field.
 

Test Plan

Line: 28 to 28
 
  • Test literal operands with National/Unicode keys (should be error)

Bugs

Changed:
<
<
  1. Errors not not thrown when literals are used with Unicode/National keys
>
>
  1. Errors not not thrown when literals are used with Unicode/National keys * Not a bug * Functions as designed.
 
  1. Records not read when using a group field that includes Unicode characters.
\ No newline at end of file

Revision 32011-04-01 - JeanNeron

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

BEG AT / END AT Statements

Line: 28 to 28
 
  • Test literal operands with National/Unicode keys (should be error)

Bugs

Changed:
<
<
  1. Errors not not thrown when literals are used with Unicode/National keys
  2. Records not read when using a group field that includes Unicode characters.
>
>
  1. Errors not not thrown when literals are used with Unicode/National keys
  2. Records not read when using a group field that includes Unicode characters.
 \ No newline at end of file

Revision 22011-03-18 - JeanNeron

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

BEG AT / END AT Statements

Line: 21 to 21
 

Test Plan

Changed:
<
<
Do RAW operands worl correctly?

Do Group operands work correctly?

Do UNICODE and NATIONAL operands work correctly?

Do literal operands work correctly with non UNICODE or NATIONAL keys?

Are correct errors thrown when trying to use literlas with UNICODE or NATIONAL keys?

>
>
  • Test with Raw operands
  • Test with Group operands
  • Test with UNICODE and NATIONAL operands
  • Test literal operands with Raw keys
  • Test literal operands with National/Unicode keys (should be error)
 

Bugs

\ No newline at end of file
Added:
>
>
  1. Errors not not thrown when literals are used with Unicode/National keys
  2. Records not read when using a group field that includes Unicode characters.

Revision 12011-03-17 - PeteBrower

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

BEG AT / END AT Statements

Overview

These statements presume that the designer has specified a field of the appropriate type or an appropriate Literal value for the Key that will be referenced on a related READNEXT or BEG READ statement.

  • RAW operand:
    • No change from the current behavior.
  • Group operand:
    • No change from the current behavior.
  • UNICODE or NATIONAL operand:
    • No change from the current behavior.
    • Must allow for length to be longer.
  • Literal operand:
    • All literal values are considered to be RAW alpha values and encoding of 8859-15.
    • Unicode escape sequences are NOT honored.
    • Literal values CANNOT be used to specify the range of records to read when the corresponding key field is a UNICODE or NATIONAL alpha field.

Test Plan

Do RAW operands worl correctly?

Do Group operands work correctly?

Do UNICODE and NATIONAL operands work correctly?

Do literal operands work correctly with non UNICODE or NATIONAL keys?

Are correct errors thrown when trying to use literlas with UNICODE or NATIONAL keys?

Bugs

 
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