@quereus/quereus 4.20.0 → 4.20.2

package/test/logic/41-generated-column-errors.sqllogic

@@ -0,0 +1,225 @@
+-- adapted from SQLite test/gencol1.test
+-- Generated-column error / rejection paths.
+
+-- ===================================
+-- 1. Self-referencing generated column rejected
+-- ===================================
+
+create table t_self (
+	id integer primary key,
+	a integer generated always as (a + 1) stored
+);
+-- error:
+drop table if exists t_self;
+
+-- ===================================
+-- 2. Mutually-recursive generated columns rejected
+-- ===================================
+
+create table t_cycle (
+	id integer primary key,
+	c0 integer not null,
+	c1 integer generated always as (c0 + c2) stored,
+	c2 integer generated always as (c1) stored
+);
+-- error:
+drop table if exists t_cycle;
+
+-- ===================================
+-- 3. DROP COLUMN of a column referenced by a GENERATED expression rejected
+-- ===================================
+
+create table t_drop (
+	id integer primary key,
+	a integer not null,
+	b integer generated always as (a * 2) stored
+);
+
+insert into t_drop (id, a) values (1, 5);
+
+-- 'a' is referenced by generated column 'b'
+alter table t_drop drop column a;
+-- error:
+
+-- dropping the generated column itself should succeed
+alter table t_drop drop column b;
+
+select id, a from t_drop where id = 1;
+→ [{"id":1,"a":5}]
+
+drop table t_drop;
+
+-- ===================================
+-- 4. A generated expression whose qualifier binds nothing is rejected at
+--    DECLARATION time, identically by CREATE TABLE and ALTER TABLE ADD COLUMN
+--
+-- A generated value is computed from the row being WRITTEN. The bare,
+-- `<table>.`, `<schema>.<table>.` and `new.` spellings all resolve to that row
+-- (see 41-generated-columns.sqllogic). `old.<col>` never resolves — there is
+-- no old row to compute from — and neither does any other qualifier that no
+-- inner FROM in the body binds. Both are rejected when the table is declared,
+-- not deferred to the first write.
+-- ===================================
+
+create table d (k integer primary key, v integer);
+insert into d values (1, 100);
+
+-- 4a. `old.<col>`, at CREATE TABLE — rejected, table not created
+create table t_old (id integer primary key, a integer,
+	g integer generated always as (old.a + 1) stored);
+-- error: binds nothing
+
+drop table t_old;
+-- error: not found in schema
+
+-- 4b. `old.<col>`, at ALTER TABLE ADD COLUMN — same rejection, table untouched
+create table t_old_alter (id integer primary key, a integer);
+insert into t_old_alter values (1, 3);
+
+alter table t_old_alter add column g integer generated always as (old.a + 1);
+-- error: binds nothing
+
+select id, a from t_old_alter order by id;
+→ [{"id":1,"a":3}]
+
+drop table t_old_alter;
+
+-- 4c. A qualifier naming a real table, but with no FROM in the body that
+--     selects from it — rejected at CREATE TABLE, table not created
+create table t_unbound (id integer primary key, a integer,
+	x integer generated always as (d.v + 1) stored);
+-- error: binds nothing
+
+drop table t_unbound;
+-- error: not found in schema
+
+-- 4d. Same qualifier, at ALTER TABLE ADD COLUMN — same rejection, table untouched
+create table t_unbound_alter (id integer primary key, a integer);
+insert into t_unbound_alter values (1, 3);
+
+alter table t_unbound_alter add column x integer generated always as (d.v + 1);
+-- error: binds nothing
+
+select id, a from t_unbound_alter order by id;
+→ [{"id":1,"a":3}]
+
+drop table t_unbound_alter;
+
+-- 4e. A qualifier bound inside the subquery — `d` — is fine; a qualifier the
+--     subquery never binds — `z` — is not, even though a subquery intervenes
+create table t_unbound_sub (id integer primary key, a integer,
+	x integer generated always as
+		((select z.v from d where d.k = a limit 1)) stored);
+-- error: binds nothing
+
+drop table t_unbound_sub;
+-- error: not found in schema
+
+-- 4f. Regression guard: a body that legitimately selects from another table
+--     still creates, inserts, and reads back — a bound qualifier stays accepted
+create table t_bound (id integer primary key, a integer,
+	x integer generated always as
+		((select d.v from d where d.k = a limit 1)) stored);
+
+insert into t_bound (id, a) values (1, 1);
+
+select id, a, x from t_bound where id = 1;
+→ [{"id":1,"a":1,"x":100}]
+
+drop table t_bound;
+
+drop table d;
+
+-- ===================================
+-- 5. A non-deterministic function in the generated body is rejected at
+--    DECLARATION time — CREATE TABLE agrees with ALTER TABLE ADD COLUMN
+--    (44.1-nondeterministic-schema.sqllogic covers the ADD COLUMN /
+--    write-time / relaxed-mode paths for the same rule).
+-- ===================================
+
+-- 5a. Rejected at CREATE TABLE, table not created
+create table t_nondet (id integer primary key,
+	x integer generated always as (random()) stored);
+-- error: Non-deterministic expression not allowed in GENERATED ALWAYS AS
+
+drop table t_nondet;
+-- error: not found in schema
+
+-- 5b. The call is found wherever it sits, not only as the whole body: nested
+--     in a larger expression, on a VIRTUAL column, and inside a subquery the
+--     body selects from.
+create table t_nondet_nested (id integer primary key, a integer,
+	x integer generated always as (a + random()) stored);
+-- error: Non-deterministic expression not allowed in GENERATED ALWAYS AS
+
+create table t_nondet_virtual (id integer primary key,
+	x integer generated always as (abs(random())) virtual);
+-- error: Non-deterministic expression not allowed in GENERATED ALWAYS AS
+
+create table t_nondet_subq (id integer primary key,
+	x integer generated always as ((select random())) stored);
+-- error: Non-deterministic expression not allowed in GENERATED ALWAYS AS
+
+-- Non-`random()` members of the non-deterministic set are caught the same way;
+-- the message names the offending function, not the whole body.
+create table t_nondet_clock (id integer primary key,
+	x text generated always as (date('now')) stored);
+-- error: Function 'date' is not deterministic
+
+-- Control: a deterministic body over the table's own columns still builds.
+create table t_det_ok (id integer primary key, a integer,
+	x integer generated always as (abs(a) + 1) stored);
+
+insert into t_det_ok (id, a) values (1, -5);
+
+select id, x from t_det_ok;
+→ [{"id":1,"x":6}]
+
+drop table t_det_ok;
+
+-- 5c. The `nondeterministic_schema` escape hatch lifts the rejection, same
+--     as it does for DEFAULT / CHECK.
+pragma nondeterministic_schema = true;
+
+create table t_nondet_relaxed (id integer primary key,
+	x integer generated always as (random()) stored);
+
+insert into t_nondet_relaxed (id) values (1);
+
+select count(*) as n, count(x) as non_null_x from t_nondet_relaxed;
+→ [{"n":1,"non_null_x":1}]
+
+drop table t_nondet_relaxed;
+
+pragma nondeterministic_schema = false;
+
+-- ===================================
+-- 6. A generated body that names the column being added inside an inner DML is a
+--    self-cycle. Everything under a DML is undecidable — the walk cannot tell
+--    whether that DML's target is this very table — and an undecidable reference
+--    records a dependency edge, so a reference to the new column's own name is a
+--    self-edge whichever way it would have resolved. `ALTER TABLE ADD COLUMN`
+--    reports it up front; the emitter's own re-analysis reaches the same answer.
+-- ===================================
+
+create table dml_src (k integer primary key, g integer);
+create table dml_t (id integer primary key);
+insert into dml_t values (1);
+
+-- 6a. Named inside the DML's RETURNING list.
+alter table dml_t add column g integer generated always as
+	((select k from (insert into dml_src values (1, 2) returning g) q limit 1));
+-- error: Cyclic dependency in generated columns
+
+-- 6b. Named inside an UPSERT assignment.
+alter table dml_t add column g integer generated always as
+	((select k from (insert into dml_src values (1, 2)
+		on conflict (k) do update set g = g + 1 returning k) q limit 1));
+-- error: Cyclic dependency in generated columns
+
+-- The rejections leave the table untouched: no `g` column was added.
+select * from dml_t;
+→ [{"id":1}]
+
+drop table dml_t;
+drop table dml_src;