SQL/MP Messages Manual

SQL Compiler Binder Messages (4000 to 4999)
HP NonStop SQL/MP Messages Manual427720-006
6-12
SQL 4045
Cause. The INSERT statement did not supply a value for the indicated column. The
column was defined with the NO DEFAULT option; therefore, the INSERT statement
must supply a value for the column.
Effect. The statement does not compile.
Recovery. Supply a value for all columns in the table or view that were defined with
the NO DEFAULT option. You can query the COLUMNS catalog table for this
information.
SQL 4046
Cause. An INSERT statement included a value for the system-defined key column for
a table or a view based on a table with key-sequenced or entry-sequenced
organization. A user or program can supply a value for the system-defined primary key
column only for relative tables or protection views based on a relative table.
Effect. The statement does not compile.
Recovery. If your application requires inserting rows into a table with explicit key
values, the table should be either a key-sequenced table with a user-defined primary
key or a relative table.
SQL 4047
Cause. An INSERT statement included a RETURNING clause, but the table did not
contain a system-defined primary key column. The RETURNING clause returns the
system-generated key value of an inserted row. If the table was defined with a user-
defined primary key, nothing is returned for an INSERT operation.
Effect. The statement does not compile.
Recovery. Check the organization of the table. If your application requires a system-
generated key value, re-create the table as a key-sequenced table without a user-
defined key, as a relative table, or as an entry-sequenced table.
4045 Column value-1 cannot assume a default value.
4046 A value for the system-defined primary key column
(SYSKEY by default) cannot be supplied for this table or view
because of its organization.
4047 The RETURNING clause is not allowed for a table or view
that does not have a system-defined primary key column
(SYSKEY by default).