Re: DB2 numeric to date conversion -- MIDRANGE-L

Subject: Re: DB2 numeric to date conversion
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Tue, 7 Nov 2023 13:57:02 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Tue, Nov 7, 2023 at 7:23 AM Rob Berendt <robertowenberendt@xxxxxxxxx> wrote:

Lots of nice suggestions. The thing I like about using Alan Campin's idate
is that it also has error trapping built in. For example, if the number is
20230931 that would be invalid. I believe idate would pass it back as a
null. You can use the other suggestions but you have to build in your own
error trapping.

Note that Alan now recommends using a date table. That lets you
leverage the SQL engine for both performance and error checking
(invalid dates aren't in the table).

John Y.

Follow-Ups:

RE: DB2 numeric to date conversion , Roger Harman

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