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.

Sign up for GitHub

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

Jump to bottom

Naming strategy is not propagated to onConflictUpdate #3144

Open
agilesteel opened this issue Nov 28, 2024 · 2 comments
Open

Naming strategy is not propagated to onConflictUpdate #3144

agilesteel opened this issue Nov 28, 2024 · 2 comments

Comments

@agilesteel
Copy link

agilesteel commented Nov 28, 2024 •
edited
Loading

Version: 4.8.5
Module: quill-jdbc-zio
Database: postgres

Expected behavior

... ON CONFLICT (foo) DO UPDATE SET a_b = EXCLUDED.a_b ...

Actual behavior

... ON CONFLICT (foo) DO UPDATE SET a_b = EXCLUDED.aB ...

Steps to reproduce the behavior

All that is required to reproduce is a PostgresZioJdbcContext(SnakeCase) and an onConflictUpdate clause.

Workaround

4.8.4 works so reverting to it is an acceptable workaround.

@getquill/maintainers
@getArtemUsername
Copy link

same for sqlite

@ngbinh
Copy link

ngbinh commented Dec 15, 2024

Looks like this change #3137 is the cause @deusaquilus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ngbinh @agilesteel @getArtemUsername