× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: null capable fields
  • From: Mark Lazarus <mlazarus@xxxxxxxx>
  • Date: Tue, 07 Sep 1999 22:43:55

Jon,

At 02:18 PM 9/6/99 -0400, you wrote:
>Simple fact of the
>matter is that most people don't even know such things exist. Of those
that do,
>a large percentage don't see the point in using them.  Even among SQL users
>(where it really makes sense tom use them) I've found that most people often
>don't use them.

 On the /400, since the automatic null support is weak, there's little
reason to use it.  Traditionally, a blank or 0 value field means no value
or invalid value.  This is the assumption and the applications were
designed to assume that.  What would null support give you that a blank /
*zero value wouldn't?

 -mark

+---
| 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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.