sqlite

changeset.c

…

changesetfuzz1.test

…

changesetfuzz.c

…

session1.test

…

session2.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

session3.test

…

session4.test

…

session5.test

…

session6.test

…

session8.test

…

session9.test

…

session_common.tcl

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

session_speed_test.c

…

sessionA.test

…

sessionat.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sessionB.test

…

sessionbig.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sessionC.test

…

sessionD.test

…

sessiondiff.test

…

sessionE.test

…

sessionF.test

…

sessionfault2.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sessionfault.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sessionG.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sessionH.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sessioninvert.test

…

sessionmem.test

…

sessionnoop2.test

Reinstate some test cases accidentally removed by [cb023fe28560ce0f].

2023-03-09 16:11:43 +00:00

sessionnoop.test

Reinstate some test cases accidentally removed by [cb023fe28560ce0f].

2023-03-09 16:11:43 +00:00

sessionrebase.test

…

sessionsize.test

…

sessionstat1.test

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sessionwor.test

…

sqlite3session.c

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

sqlite3session.h

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00

test_session.c

Add the SQLITE_CHANGESETAPPLY_IGNORENOOP flag, which may be passed to sqlite3changeset_apply_v2() to have it ignore changes that would be no-ops if applied to the database (e.g. deleting a row that has already been deleted), instead of considering them conflicts.

2023-03-08 18:03:04 +00:00