RE: Hex '00' to Hex '40'?

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

Nope.
If you have interactive SQL, try this fun exercise:
CREATE TABLE BUCK/SQLSAMPLE (FIELD1 CHAR (1) WITH DEFAULT 'X')
INSERT INTO BUCK/SQLSAMPLE (FIELD1) VALUES('A')
update buck/sqlsample set field1=null where field1='A'
select * from buck/sqlsample          (shows "-" meaning NULL)

exit SQL and do a DSPPFM BUCK/SQLSAMPLE:
You'll find that the field'd value is the default of 'X' even though it's
NULL indicator is set.
It's been an education for me, too!

Buck

> -----Original Message-----
> From: Howard Weatherly 
> Sent: Wednesday, June 30, 1999 3:56 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Hex '00' to Hex '40'?
> 
> Ok Buck, I see what you are getting at! but.... If I...
> 
> EXEC SQL UPDATE DB.OWN.TB SET FIELD_NAME=NULL END-EXEC
> 
> Will the field FIELD_NAME not contain NULL represented as x'00'?
>      
> 
> Buck Calabro wrote:
> > 
> > There is no null "value" - only the null indicator.  The two are
> separate,
> > distinct and unrelated.  It was a bit of a leap for me too, until I
> realised
> > that they really do need to keep them separate.  I now think of the null
> > indicator as another attribute of the field, like it's length, data type
> and
> > value.
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---