Inserts a row into the named cursor. Values for the columns are taken from the first SQLDA or the host variable list, in a
one-to-one correspondence with the columns in the INSERT statement (for an INSERT cursor) or the columns in the SELECT list
(for a SELECT cursor).
The PUT statement can be used only on a cursor over an INSERT or SELECT statement that references a single table in the FROM
clause, or that references an updatable view consisting of a single base table.
If the sqldata pointer in the SQLDA is the null pointer, no value is specified for that column. If the column has a DEFAULT
VALUE associated with it, that is used; otherwise, a NULL value is used.
The second SQLDA or host variable list contains the results of the PUT statement.
The optional ARRAY clause can be used to perform wide puts, which insert more than one row at a time and which may improve
performance. The integer value is the number of rows to be inserted. The SQLDA must contain a variable for each entry (number
of rows * number of columns). The first row is placed in SQLDA variables 0 to (columns per row)-1, and so on.
Note
For scroll (value-sensitive) cursors, the inserted row will appear if the new row matches the WHERE clause and the keyset
cursor has not finished populating. For dynamic cursors, if the inserted row matches the WHERE clause, the row may appear.
Insensitive cursors cannot be updated.
When inserting rows into a value-sensitive (keyset driven) cursor, the inserted rows appear at the end of the result set,
even when they do not match the WHERE clause of the query or if an ORDER BY clause would normally have placed them at another
location in the result set.