Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SET COLLATE vs Relational Operators #21

Open
lscheffler opened this issue Jun 23, 2022 · 0 comments
Open

SET COLLATE vs Relational Operators #21

lscheffler opened this issue Jun 23, 2022 · 0 comments

Comments

@lscheffler
Copy link

lscheffler commented Jun 23, 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:

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.

lscheffler added a commit to lscheffler/HelpFile that referenced this issue Jun 24, 2022
This was referenced Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant