You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both help topics should highlight that SET COLLATION changes the behaviour of Relational Operators for Strings.
This is the Relational Operators<; >; =: <>; #; !=;; <=; >= change there behaviour is SET COLLATE TO "MACHINE" is active or not.
The string comparison == is not affected.
Example:
SET COLLATE TO "GENERAL"
?"GALA"= "Gala"
?"A"= "a"
SET COLLATE TO "MACHINE" && binary
?"GALA"= "Gala"
?"A"= "a"
On the SET COLLATE topic there is a minor
Using a collating sequence other than MACHINE may reduce performance primarily in comparison and ...
But this not a hint to the problem.
I guess it should go into the Remarks section.
Add the other topic to the "See Also" sections.
The text was updated successfully, but these errors were encountered:
lscheffler
added a commit
to lscheffler/HelpFile
that referenced
this issue
Jun 24, 2022
Both help topics should highlight that SET COLLATION changes the behaviour of Relational Operators for Strings.
This is the Relational Operators
<; >; =: <>; #; !=;; <=; >=
change there behaviour is SET COLLATE TO "MACHINE" is active or not.The string comparison
==
is not affected.Example:
On the SET COLLATE topic there is a minor
I guess it should go into the Remarks section.
Add the other topic to the "See Also" sections.
The text was updated successfully, but these errors were encountered: