From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,cfd23c10fd537a80 X-Google-Attributes: gid103376,public From: Geoff Bull Subject: Re: Ada Calendar oddity Date: 2000/05/11 Message-ID: <391AB866.23686FFB@acenet.com.au>#1/1 X-Deja-AN: 622108017 Content-Transfer-Encoding: 8bit References: <39176D85.603D7AEC@research.canon.com.au> <39178DEA.FD2C20FA@research.canon.com.au> <8f92o1$6v$1@nnrp1.deja.com> <3918BB77.693C70D6@research.canon.com.au> <8fahfv$mgt$1@nnrp1.deja.com> <3919CC94.538DDBA0@online.no> X-Accept-Language: en Content-Type: text/plain; charset=iso-8859-1 X-Complaints-To: abuse@telstra.net X-Trace: nsw.nnrp.telstra.net 958052644 203.35.118.1 (Thu, 11 May 2000 23:44:04 EST) Organization: Customer of Telstra Big Pond Direct MIME-Version: 1.0 NNTP-Posting-Date: Thu, 11 May 2000 23:44:04 EST Newsgroups: comp.lang.ada Date: 2000-05-11T00:00:00+00:00 List-Id: "Tarjei Tj�stheim Jensen" wrote: > > > If one wanted to use the Year type in Ada.Calendar for birthday and > > expiration date, one would get an constraint error when one issued > > drivers licences for these born this year. Wouldn't one? > That would be a wrong use of the type. The drivers license "problem" is > a database issue. You should not use something that is internal to Ada > in that context. So when you read a date from the database, what type should you use? If you avoid using Ada.Calendar how do you compare the database time with the today's date, e.g.?