aljaz/turso
1
0
Fork 0
mirror of https://github.com/aljazceru/turso.git synced 2026-02-23 00:45:37 +01:00
Code Issues Packages Projects Releases Wiki Activity

panic when on_conflict is specified for Unique constraint

Browse Source
This commit is contained in:
pedrocarlo
2025-05-10 18:13:58 -03:00
parent e7d0962a6c
commit 5dee1adab8
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
core/schema.rs
View File

@@ -314,9 +314,12 @@ fn create_table(
}
} else if let limbo_sqlite3_parser::ast::TableConstraint::Unique {
columns,
conflict_clause: _, // TODO: ignore conflict_cause for now
conflict_clause,
} = c.constraint
{
if conflict_clause.is_some() {
unimplemented!("ON CONFLICT not implemented");
}
let unique_set: Vec<_> = columns
.into_iter()
.map(|column| {
@@ -412,7 +415,10 @@ fn create_table(
default = Some(expr.clone())
}
// TODO: for now we don't check Resolve type of unique
limbo_sqlite3_parser::ast::ColumnConstraint::Unique(..) => {
limbo_sqlite3_parser::ast::ColumnConstraint::Unique(on_conflict) => {
if on_conflict.is_some() {
unimplemented!("ON CONFLICT not implemented");
}
unique = true;
}
_ => {}