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

implement SQLite DDL level ON CONFLICT #4360

Closed
sqlalchemy-bot opened this issue Nov 7, 2018 · 2 comments
Closed

implement SQLite DDL level ON CONFLICT #4360

sqlalchemy-bot opened this issue Nov 7, 2018 · 2 comments
Labels
feature sqlite
Milestone
1.3

Comments

@sqlalchemy-bot
Copy link
Collaborator

Migrated issue, originally created by Michael Bayer (@zzzeek)

moved from #4010 to represent straight ON CONFLICT, that is, https://www.sqlite.org/lang_conflict.html.

https://gerrit.sqlalchemy.org/#/c/zzzeek/sqlalchemy/+/700/
@sqlalchemy-bot
Copy link
Collaborator Author

Michael Bayer (@zzzeek) wrote:

Implement SQLite ON CONFLICT for constraints

Implemented the SQLite ON CONFLICT clause as understood at the DDL
level, e.g. for primary key, unique, and CHECK constraints as well as
specified on a :class:.Column to satisfy inline primary key and NOT NULL.
Pull request courtesy Denis Kataev.

Fixes: #4360
Change-Id: I4cd4bafa8fca41e3101c87dbbfe169741bbda3f4
Pull-request: zzzeek/sqlalchemy#431

→ de804d7

@sqlalchemy-bot
Copy link
Collaborator Author

Changes by Michael Bayer (@zzzeek):

  • changed status to closed

@sqlalchemy-bot sqlalchemy-bot added this to the 1.3 milestone Nov 27, 2018
@typicalTYLER typicalTYLER mentioned this issue Mar 25, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature sqlite
Projects
None yet
Milestone
1.3
Development

No branches or pull requests
1 participant
@sqlalchemy-bot