Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Date format RR limitations. (adding; Please answer, Thomas Kyte!)

Re: Date format RR limitations. (adding; Please answer, Thomas Kyte!)

From: Arjan van Bentem <avbentem_at_DONT-YOU-DAREdds.nl>
Date: Wed, 3 Mar 1999 07:14:52 +0100
Message-ID: <36dcd363$0$13308@pascal>


Remco Blaakmeer wrote
>if you are sure that by then your database contains
>no dates older than Jan 1st, 2000.

No. It does not matter at all if you ave dates prior to 2000 in your database. The datemask will only be used for input or output, but not for any calculations or order by clauses. That is: if you use date functions like documented.

>The same goes, of course, for using the RR format now. If your database
>contains data older than Jan 1st, 1950, you should not use the RR
>format.

See above. It does *not* matter. Oracle always stores the dates fully Y2k compliant (and has done since a long time), regardless whether it is in the 14th or 22nd century. It just is inputting two-digits years that gives you the problem. Using RR, or even better RRRR for the input mask just helps you to get the dates into the database. However, it is really a nice add-on to help make your apps Y2k compliant. New apps should definitly use YYYY.

Arjan. Received on Wed Mar 03 1999 - 00:14:52 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US