×
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.
The null does add some logic complexity. Right now I just say "if today is > expires" do something. With null values that would need to be "if not null and today is > expires"
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, February 28, 2008 12:12 PM
To: Java Programming on and around the iSeries / AS400
Subject: Re: jt400 timestamp issue
Mike Cunningham wrote:
Good point from both you and David. It really should be a null field
but the original reason I posted this was a problem where the driver
was sending a null value and the java application using the driver
puked on the null value. If I had it set to null that problem would
still exist.
Well, if you set the field to null capable, then you should be check to
see if it's null or not before processing the contents.
One of the reasons I really don't like the idea of null capable fields
is that support for null fields isn't all that uniform.
david
--
IBM System i - For when you can't afford to be out of business
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/java400-l.
midrange.com
