opt: nextval argument must be qualified for CREATE VIEW, CREATE TABLE AS

[RaduBerinde]

For CREATE VIEW and CREATE TABLE AS, the optimizer rewrites the SQL statement to fully qualify object names. This does not include the sequence name argument to nextval and similar.

root@127.144.215.162:45189/movr> select nextval('seq');
  nextval  
+---------+
        3  
(1 row)

root@127.144.215.162:45189/movr> create table t as select nextval('seq');
pq: nextval(): relation "seq" does not exist

Similar problem with views:

root@127.144.215.162:45189/movr> create view v as select nextval('seq');
CREATE VIEW

root@127.144.215.162:45189/movr> select * from v;
  nextval  
+---------+
       12  
(1 row)

root@127.144.215.162:45189/movr> use d;
SET

root@127.144.215.162:45189/d> select * from movr.v;
pq: nextval(): relation "seq" does not exist

Jira issue: CRDB-5507

[github-actions]

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
5 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

[github-actions]

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!