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

<=> operator not getting formatted correctly #432

Closed
kathykwon opened this issue Jun 7, 2023 · 3 comments · Fixed by #433
Closed

<=> operator not getting formatted correctly #432

kathykwon opened this issue Jun 7, 2023 · 3 comments · Fixed by #433
Labels
enhancement New feature or request

Comments

@kathykwon
Copy link

kathykwon commented Jun 7, 2023

Describe the bug
The <=> operator is not getting formatted correctly.

To Reproduce

select * from foo join bar on foo.baz <=> bar.baz

Expected behavior

select * from foo join bar on foo.baz <=> bar.baz

Actual behavior

select * from foo join bar on foo.baz <= > bar.baz

Additional context
Running v0.18.0 on a pre-commit hook.

  - repo: https://github.com/tconbeer/sqlfmt
    rev: v0.18.0
    hooks:
      - id: sqlfmt
        language_version: python
        additional_dependencies: [".[jinjafmt]"]
@kathykwon kathykwon changed the title <=> operator not getting formatted correctly <=> operator not getting formatted correctly Jun 7, 2023
@tconbeer
Copy link
Owner

tconbeer commented Jun 7, 2023

This should be an easy fix. What is this operator? I don't think it's Postgres-compatible?

@kathykwon
Copy link
Author

This should be an easy fix. What is this operator? I don't think it's Postgres-compatible?

null safe equal
not sure about postgres compatibility

@tconbeer
Copy link
Owner

tconbeer commented Jun 7, 2023

Huh. Thanks!

@tconbeer tconbeer added the enhancement New feature or request label Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants