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

SQLite backend isn't using returning #653

Open
andoriyu opened this issue Mar 31, 2022 · 1 comment · May be fixed by #654
Open

SQLite backend isn't using returning #653

andoriyu opened this issue Mar 31, 2022 · 1 comment · May be fixed by #654

Comments

@andoriyu
Copy link

Summary

I would like to use returning branch in update and insert when using sqlite.

Motivation

It's more efficient than looking up by primary id after update.

Additional Information

SQLite's support for RETURNING
@andoriyu andoriyu linked a pull request Mar 31, 2022 that will close this issue
Open
@billy1624 billy1624 moved this to Triage in SeaQL Dev Tracker Jul 7, 2022
@billy1624 billy1624 moved this from Triage to Next Up in SeaQL Dev Tracker Jul 7, 2022
@billy1624
Copy link
Member

Hey @andoriyu, sorry for the delay but before we proceed with the PR: #654
We need to have a consensus on this: #654 (comment)

@billy1624 billy1624 moved this from Next Up to Triage in SeaQL Dev Tracker Jan 13, 2023
@acrrd acrrd mentioned this issue Jan 18, 2024
Merged
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
SeaQL Dev Tracker
Status: Triage
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Mark SQLite backend as "returning" andoriyu/sea-orm
2 participants
@andoriyu @billy1624