HP3000-L Archives

October 1995, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
henryck halsey <[log in to unmask]>
Reply To:
henryck halsey <[log in to unmask]>
Date:
Thu, 12 Oct 1995 03:25:21 MEZ
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Wirt wrote:
>
> But there is a second productivity attribute, too, and that is
processing
> time. Let us presume that requirement is to find all of the
invoices for May,
> regardless of the year, and the date is numerically encoded as
a Julian date,
> offset from some arbitrary date, as it is MANMAN, then the
query must be
> formulated something like this (using a generic query syntax):
>
>      find when
substring(ascii(date(jd(DATE-DATAITEM,offset)))) = 05
>
> In comparison, if the date were text-field encoded, the same
query would be:
>
>      find when DATE-DATAITEM(3,4) = 05
 
Many interesting and knowledgeable points have been made on this
subject, but there is something mildly reassuring in the
knowledge that my humble Quiz or QTP code can trawl through
MANMAN databases anywhere in the world and not have to worry
about YYMMDD/YYDDMM/ etc.
 
Regards,
Henryk.

ATOM RSS1 RSS2