RE: Insert of null-values with RPG, SQL or DFU

Alexander Brand wrote:

>We found a different behavior 
>between SQL/400 and RPG. 
>When you insert a row into 
>a table without specifying values for 
>nulls-allowed columns with RPG 
>it inserts default values. This value
>is not null, in contrast to the SQL 
>(ISO) defined behavior. 
>
>How can you "teach" RPG to 
>behave like standard SQL in general,
>avoiding to set the null-indicator 
>for each single column?

As far as I know, you can't as of V4R3.  I haven't studied the V4R4 manuals
and behaviour in detail yet.

One thing that you must realise is that NULL is not a value - it is an
attribute.  A column can have a value of 1.00 and also an attribute of NULL.
SQL "masks" this by not displaying the value if NULL is set.  We're forced
so either use the null map or %nullind for each field.

Annoying, isn't it?

Buck Calabro
Aptis; Albany, NY
"We are what we repeatedly do.
 Excellence, then, is not an act, but a habit." --Aristotle


Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---