[tarantool-patches] Re: [PATCH v3 2/4] sql: an ability to disable CK constraints

[Konstantin Osipov]

* Kirill Shcherbatov <kshcherbatov at tarantool.org> [19/09/16 15:49]:
> Closes #4244
> 
> @TarantoolBot document
> Title: an ability to disable CK constraints
> 
> Now it is possible to disable and enable ck constraints.
> This option is not persistent. All ck constraints are enabled
> by default when Tarantool is configured. Ck constraints checks
> are not performed during standard recovery, but performed during
> force_recovery - all conflicting tuples are skipped in case of
> ck_constraint conflict.
> 
> To change CK constraint "is_enabled" state, call
> -- in LUA
> ck_obj:enable(new_state in {true, false})
> -- in SQL
> ALTER TABLE {TABLE_NAME} {EN, DIS}ABLE CONSTRAINT {CK_NAME};

ALTER TABLE should persist its results - it's a rule with no
known exception. Why can't you persist it?

-- 
Konstantin Osipov, Moscow, Russia