Another missing normalization tbl name issue on INSERT RETURNING.
Similiar: #2817 #2744 #2697
turso> create table "users" (id integer primary key, name text);
turso> insert into "users" values (1, 'a') returning "users".id, "users".name;
× Parse error: no such table: users
turso> insert into "users" values (2, 'b') returning users.id, users.name;
× Parse error: no such table: users
turso> delete from "users" where id = 1 returning "users".id, "users".name;
┌────┬──────┐
│ id │ name │
├────┼──────┤
│ 1 │ a │
└────┴──────┘
turso> update "users" set name='c' where id=2 returning "users".id, "users".name;
┌────┬──────┐
│ id │ name │
├────┼──────┤
│ 2 │ c │
└────┴──────┘
sqlite> insert into "users" values (1, 'a') returning "users".id, "users".name;
┌────┬──────┐
│ id │ name │
├────┼──────┤
│ 1 │ a │
└────┴──────┘
INSERT stores the joined-table identifier via Name::to_string (preserves original quoting), while DELETE/UPDATE pass it through normalize_ident first — so qualified RETURNING refs only fail on INSERT.
Another missing normalization tbl name issue on INSERT RETURNING.
Similiar: #2817 #2744 #2697
INSERT stores the joined-table identifier via
Name::to_string(preserves original quoting), while DELETE/UPDATE pass it throughnormalize_identfirst — so qualified RETURNING refs only fail on INSERT.