4GL/ABL: Why does a CASE-SENSITIVE compare with BEGINS in a query (FOR EACH) not work, when the collation (-cpcoll) is not BASIC? - Progress Community

Loading

Skip to Main Content

4GL/ABL: Why does a CASE-SENSITIVE compare with BEGINS in a query (FOR EACH) not work, when the collation (-cpcoll) is not BASIC?

A CASE-SENSITIVE compare with BEGINS in a query (FOR EACH) is not working, when collation (-cpcoll) is not BASIC (for example ICU-UCA).

May 11, 2021
Knowledge

Title

4GL/ABL: Why does a CASE-SENSITIVE compare with BEGINS in a query (FOR EACH) not work, when the collation (-cpcoll) is not BASIC?

URL Name

4GL-ABL-Why-does-a-CASE-SENSITIVE-compare-with-BEGINS-in-a-query-FOR-EACH-not-work-when-the-collation-cpcoll-is-not-BASIC

Article Number

000202239

Environment

Product: OpenEdge Version: 12.x OS: Windows Other: N/A

Question/Problem Description

Why does a CASE-SENSITIVE compare with BEGINS in a query (FOR EACH) not work, when the collation (-cpcoll) is not BASIC?

Steps to Reproduce

/* test.p */ DEFINE TEMP-TABLE tt_temp NO-UNDO FIELD some_field AS CHARACTER CASE-SENSITIVE INDEX standard IS PRIMARY UNIQUE some_field . CREATE tt_temp. ASSIGN tt_temp.some_field = "-D 1024". CREATE tt_temp. ASSIGN tt_temp.some_field = "-d dmy". DEFINE VARIABLE i AS INTEGER NO-UNDO. DEFINE VARIABLE j AS INTEGER NO-UNDO. FOR EACH tt_temp NO-LOCK WHERE tt_temp.some_field BEGINS "-D": i = i + 1. END. FOR EACH tt_temp NO-LOCK WHERE tt_temp.some_field MATCHES "-D*": j = j + 1. END. MESSAGE "BEGINS: " i SKIP "MATCHES: " j VIEW-AS ALERT-BOX. /* With -cpcoll ICU-UCA --------------------------- BEGINS: 2 MATCHES: 1 --------------------------- */ /* With -cpcoll Basic --------------------------- BEGINS: 1 MATCHES: 1 --------------------------- */ /* ent122utf8.pf */ -E # european numeric format -d dmy # date format -lng "German" # language -cpcase Basic # case table -cpcoll Basic # collation table -cpinternal UTF-8 # code page -cpstream UTF-8 # code page -cpterm IBM850 # code page - Run test.p as: prowin test.p -pf ent122utf8.pf

Clarifying Information

Error Message

Defect Number

OCTA-31967

Enhancement Number

Cause

Resolution

Until the fix is available, use the workaround below.

Workaround

Use the COMPARE statement in place of the BEGINS statement in the query. For example:

FOR EACH <table> WHERE
COMPARE(<field>,"BEGINS","O","case-insensitive","basic9") NO-LOCK

The COMPARE statement can take a BEGINS operator, which will honor the collation and return the correct results when used in a WHERE clause. As this is a non-indexed field, using COMPARE will have a similar performance impact to using BEGINS (i.e. it has to be evaluated instead of using an index).

Another example:

FOR EACH tt_temp NO-LOCK WHERE COMPARE(tt_temp.some_field,"BEGINS","-D","case-sensitive","ICU-UCA"):
i = i + 1.
END

NOTE: Starting the session with -collop 1 breaks the work around.

Notes

Keyword Phrase

Last Modified Date

2/15/2023 5:45 PM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

4GL/ABL: Why does a CASE-SENSITIVE compare with BEGINS in a query (FOR EACH) not work, when the collation (-cpcoll) is not BASIC? - Progress Community