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



Shouldn't you be using BIGINT for large integers like that.

Also, I thought that it was defined as 9P0 when I was playing with it a
while back.

On Tue, Apr 29, 2008 at 10:44 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

This is sort of an RPG thing, but really more of a DB2 issue, which is
why I posted it here.

Dave Odom ought to love this. It may have been discussed before, but I
didn't find it. Anyway, if you declare a field in SQL as type INT, it
is actually declared in DB2 as a 9B0 field. This is fine right up until
the time you try to write a value over 999,999,999. For example:
1,198,368,000, which is the number of seconds between January 1, 2008
and January 1, 1970.

Such joy.

Joe
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.