|
GokhanYe wrote: >>I think, Allow null values (ALWNULL) option should be set to *USRCTL before >compile. Yes, I set the option to *USRCTL. John wrote: >In SQL if I want to write a column as null, I would manipulate the >associated Indicator Variable (the 4 byte binary) to a value of -1 for the >particular column I wanted Null. You don't set the column itself to a >"NULL" value. As you correctly said, the Null state is an attribute of a >>column NOT a value of the column. Yes, the Null state is an attribute, but I don't need to manipulate the Indicator Variable. You can set a NULL value: INSERT INTO customer (name, country, telephon) VALUES ( 'Smith Robert', 'Canada', NULL) or INSERT INTO customer (name, country) VALUES ( 'Smith Robert', 'Canada') The result ist the same, because the column "telephon" is a null-capable field and won't be initialized with *ZEROS, it is unused . But in RPG you write a record as follows: EVAL name = 'Smith Robert' EVAL country = 'Canada' WRITE customer The column "telephon" is set to *ZEROS because RPG initialize it automatically. It isn't practicable to set the null indicator for EACH null-capable column with %NULLIND! The result are two different records: NAME COUNTRY TELEPHON Smith Robert Canada - (NULL value from SQL) Smith Robert Canada 0 (*ZERO value from RPG ) It isn't practicable to set the null indicator for EACH null-capable column with %NULLIND! I have a bigger problem with date fields. When a record is inserted (via rpg) the date field has a default value = 0001-01-01. When a record is inserted (via SQL) the field has a NULL value. alex +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.