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

Feature Request: Place ON CONFLICT on new line #535

Closed
markhilb opened this issue Nov 29, 2022 · 2 comments · Fixed by #544
Closed

Feature Request: Place ON CONFLICT on new line #535

markhilb opened this issue Nov 29, 2022 · 2 comments · Fixed by #544
Labels

Comments

@markhilb
Copy link

Describe the Feature
Place ON CONFLICT on new line.

Current behaviour:

INSERT INTO
    tests (val)
VALUES
    (1),
    (2) ON CONFLICT (val)
DO NOTHING;

Wanted behaviour:

INSERT INTO
    tests (val)
VALUES
    (1),
    (2) 
ON CONFLICT (val)
DO NOTHING;
@nene
Copy link
Collaborator

nene commented Nov 29, 2022

Another problem in here really is that DO NOTHING gets placed on a new line. This only happens with MySQL, MariaDB, SingleStoreDB and PostgreSQL (though not sure if ON CONFLICT clause is valid syntax in all of them).

@nene
Copy link
Collaborator

nene commented Dec 15, 2022

This is now fixed in 12.0.4 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants