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

improvement: support {:unsafe_fragment, ".."} as a conflict target #129

Merged

Conversation

zachdaniel
Copy link
Contributor

this is supported by other sql data layers, for example. This is necessary for AshSqlite3's upsert behavior. Postgres adapter implementation: https://github.com/elixir-ecto/ecto_sql/blob/v3.10.2/lib/ecto/adapters/postgres/connection.ex#L212C4-L213C26

@zachdaniel zachdaniel force-pushed the unsafe-fragment-conflict-target branch from 7b97dce to d03824e Compare October 10, 2023 19:00
@warmwaffles
Copy link
Member

This looks good. I'll merge it once CI passes. It would be nice to have a test added for this. I don't know if there are unsafe fragment tests in the integration suite provided by ecto_sql and ecto.

@zachdaniel
Copy link
Contributor Author

👍 will add one

@zachdaniel zachdaniel force-pushed the unsafe-fragment-conflict-target branch from d03824e to fe54500 Compare October 10, 2023 19:18
this is supported by other sql data layers, for example. This is necessary for AshSqlite3's upsert behavior.
Postgres adapter implementation: https://github.com/elixir-ecto/ecto_sql/blob/v3.10.2/lib/ecto/adapters/postgres/connection.ex#L212C4-L213C26
@zachdaniel zachdaniel force-pushed the unsafe-fragment-conflict-target branch from fe54500 to d6d5f11 Compare October 10, 2023 19:19
@zachdaniel
Copy link
Contributor Author

Alright, added a test :)

@warmwaffles warmwaffles merged commit e99c33d into elixir-sqlite:main Oct 10, 2023
9 checks passed
@warmwaffles
Copy link
Member

Perfect!

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

Successfully merging this pull request may close these issues.

2 participants