× 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.


  1.  Home
  2. RPG400-L
  3. April 2010

Re: AW: SQL null indicators when not all columns are null capable

Nathan Andelin wrote:

We occasionally have to write an extra "if" statement that
outputs an empty string to a browser field when a date field
contains *loval. That's actually pretty rare because we normally
call procedures to properly format date fields into character
strings.

The use of scalars such as COALESCE() and IFNULL() when selecting the data for output via SQL, typically eliminates such if-statement logic in the programs.

But it always seems easier to handle *loval situations than *null
situations, so we never allow *nulls in our database tables.

Any specific example that might elucidate that opinion?

Regards, Chuck

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.