/insert generates unexpected 'N/A' string for a blob column & data too long for vc20

[stevemuench]

When creating a table with a blob, and requesting the generation of sample data, Quick SQL unexpectedly provides the literal string 'N/A' as the sample data value for the blob

reports /insert 1
        created date
        description vc20
        pdf blob

This produces:

insert into reports (
id,
created,
description,
pdf
) values (
1,
sysdate-70,
'Om pikawo pe amopi woem efum ji ga sefze figi pomlot dadeziguz seak nigamu luv. Boma oziworpaz re cuznim reletwaj lojeibe lolmuj tujle tovufmu vofizo nuzi regusoj iwmum busifurih weof.',
'N/A'
);

This generated insert statement has two problems. The 'N/A' produces an error ORA-01465: invalid hex number and the sample data for the vc20 column description produces an error ORA-12899: value too large for column

A workaround for the blob issue is to use the /values null on the blob column and a workaround for the vc issue is to use a /values One Value,Another Value,Something Else,Fourth Example like this:

reports /insert 1
        created date
        description vc20 /values One Value,Another Value,Something Else,Fourth Example
        pdf blob /values null