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

Comment out tests that require COLLLATE in unique index creation

Browse Source
This commit is contained in:
PThorpe92
2025-08-29 20:36:29 -04:00
parent e4a0a57227
commit 3ab2126c89
1 changed files with 33 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

62
testing/upsert.test
View File

@@ -192,35 +192,6 @@ do_execsql_test_on_specific_db {:memory:} upsert-collate-implicit-match {
SELECT * FROM ci;
} {Alice|2}
# Target specifies BINARY but the unique index is NOCASE: target should NOT match, so expect error
do_execsql_test_in_memory_any_error upsert-collate-target-mismatch {
CREATE TABLE cm (name TEXT, v);
CREATE UNIQUE INDEX cm_name_nocase ON cm(name COLLATE NOCASE);
INSERT INTO cm VALUES ('Alice', 1);
INSERT INTO cm VALUES ('aLiCe', 2)
ON CONFLICT(name COLLATE BINARY) DO UPDATE SET v = excluded.v;
}
# Omitted target must apply to conflicts on any UNIQUE/PK, should update on NOCASE index.
do_execsql_test_on_specific_db {:memory:} upsert-collate-omitted-target-matches {
CREATE TABLE co (name TEXT, v);
CREATE UNIQUE INDEX co_name_nocase ON co(name COLLATE NOCASE);
INSERT INTO co VALUES ('Alice', 1);
INSERT INTO co VALUES ('aLiCe', 9)
ON CONFLICT DO UPDATE SET v = excluded.v;
SELECT * FROM co;
} {Alice|9}
# Composite unique with mixed collations, orderless target with explicit NOCASE on the first key.
do_execsql_test_on_specific_db {:memory:} upsert-composite-collate-orderless {
CREATE TABLE cc (name TEXT, city TEXT, val);
CREATE UNIQUE INDEX cc_nc ON cc(name COLLATE NOCASE, city); -- name NOCASE, city default/BINARY
INSERT INTO cc VALUES ('Alice','SF','old');
INSERT INTO cc VALUES ('aLiCe','SF','new')
ON CONFLICT(city, name COLLATE NOCASE) DO UPDATE SET val = excluded.val;
SELECT * FROM cc;
} {Alice|SF|new}
# Composite index requires exact coverage, targeting too few columns must not match.
do_execsql_test_in_memory_any_error upsert-composite-target-too-few {
CREATE TABLE ct (a, b, val);
@@ -342,3 +313,36 @@ do_execsql_test_on_specific_db {:memory:} upsert-doubly-qualified-target {
ON CONFLICT(main.dq.a) DO UPDATE SET b = excluded.b;
SELECT * FROM dq;
} {1|new}
# TODO: uncomment these when we support collations in indexes
# (right now it errors on Parse Error: cannot use expressions in CREATE INDEX)
#
# Target specifies BINARY but the unique index is NOCASE: target should NOT match, so expect error
# do_execsql_test_in_memory_any_error upsert-collate-target-mismatch {
# CREATE TABLE cm (name TEXT, v);
# CREATE UNIQUE INDEX cm_name_nocase ON cm(name COLLATE NOCASE);
# INSERT INTO cm VALUES ('Alice', 1);
# INSERT INTO cm VALUES ('aLiCe', 2)
# ON CONFLICT(name COLLATE BINARY) DO UPDATE SET v = excluded.v;
# }
#
# do_execsql_test_on_specific_db {:memory:} upsert-collate-omitted-target-matches {
# CREATE TABLE co (name TEXT, v);
# CREATE UNIQUE INDEX co_name_nocase ON co(name COLLATE NOCASE);
# INSERT INTO co VALUES ('Alice', 1);
# INSERT INTO co VALUES ('aLiCe', 9)
# ON CONFLICT DO UPDATE SET v = excluded.v;
# SELECT * FROM co;
# } {Alice|9}
#
#
# do_execsql_test_on_specific_db {:memory:} upsert-composite-collate-orderless {
# CREATE TABLE cc (name TEXT, city TEXT, val);
# CREATE UNIQUE INDEX cc_nc ON cc(name COLLATE NOCASE, city);
# INSERT INTO cc VALUES ('Alice','SF','old');
# INSERT INTO cc VALUES ('aLiCe','SF','new')
# ON CONFLICT(city, name COLLATE NOCASE) DO UPDATE SET val = excluded.val;
# SELECT * FROM cc;
# } {Alice|SF|new}