Kontakt

Ansicht
Dokumentation

ABENWHERE_LOGEXP_COMPARE - WHERE LOGEXP COMPARE

ABENWHERE_LOGEXP_COMPARE - WHERE LOGEXP COMPARE

CL_GUI_FRONTEND_SERVICES - Frontend Services   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Short Reference

- Comparison Operators

... operand1 operator operand2
                    $| ${ $[ALL$|ANY$|SOME$] ( SELECT subquery_clauses )$} ...

Effect

This relational expression compares the content of the operand operand1 in accordance with the comparison operator operator with the content of the operand operand2 or with the result of a scalar subquery.

  • The following can be specified for operand1 on the left side:

  • The following can be specified for operand2 on the left side:

Here, a column col must be specified as data_source~comp, or tabalias~comp using the column selector and it must be possible to compare the data types of the left side and right side.

The content of an ABAP object, that is, an untyped literal, a host variable, or a host expression) must match the data type of operand1 in accordance with the rules for lossless assignments. This is checked by the strict modes of the syntax check from Release and can raise an exception.

The following table shows the possible comparison operators:

operator Meaning
=, EQ True if the content of operand1 is equal to the content of operand2.
<>, NE True if the content of operand1 is not equal to the content of operand2.
, LT True if the content of operand1 is less than the content of operand2.
>, GT True if the content of operand1 is greater than the content of operand2.
=, LE True if the content of operand1 is less than or equal to the content of operand2.
>=, GE True if the content of operand1 is greater than or equal to the content of operand2.

The following should be noted when using these operators:

  • Comparisons between columns or between SQL expressions (including typed literals and aggregate expressions) and columns are performed completely on the database. No type conversions are made in ABAP beforehand. If the data types or lengths on the left and right side do not match, the resulting behavior depends entirely on the conversion rules of the database, where fewer conversions are generally possible here than in ABAP. The platform-dependent behavior can produce different results or even SQL errors on individual platforms.
  • The decimal places are respected in comparisons between numeric types.
  • In greater than/less than comparisons with character-like types, the result can depend on the code page used by the database system. This applies in particular to the non-printable characters.
  • Trailing blanks are usually ignored in comparisons between character-like types.
  • In the case of columns that contain nothing but a blank character, it depends on the platform how this blank is saved:
  • In the SAP HANA database and in MaxDB a single blank is saved as an empty string and not as specified by the code page in question.

  • In all other database and in table buffering, a single blank is saved in accordance with the code page.

This means that the behavior produced when a value of this type is selected using size comparisons depends on the platform and buffering. More specifically, a single blank in the SAP HANA database and in MaxDB is not found in the interval of all possible characters.

Notes

  • The obsolete forms >, =, and => of comparison operators may still appear outside of classes.
  • Size comparisons for character-like operands should be avoided to prevent platform-dependent behavior. An exception here are simple cases, such as operands that contain only digits.

Example

Reading of flights with a seat occupancy that is less than the entered value.

Example

Reading of overbooked flights.






General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 8887 Date: 20240420 Time: 115408     sap01-206 ( 101 ms )