Re: Using 12/31/9999 in a date field

From: Jonathan Lewis <>
Date: Thu, 19 Dec 2013 07:57:53 -0000
Message-ID: <D20E3BA99A5D467288DF9D22DB25F0C3_at_Primary>

That's a very good point, of course.

There are a number of side effects that could follow from (a) indexing on just a date-only column, and (b) indexing a column where a single value can have a large number of rows (especially with a constant stream of new rows appearing and old rows disappearing). You may be heading for the worst possible combination - though how much that matters does depend to a very large extent on the actual pattern of use of the column.


Jonathan Lewis

Author: Oracle Core (Apress 2011)

  • Original Message ----- From: "Michael Haddon" <> To: <> Sent: Thursday, December 19, 2013 12:54 AM Subject: Re: Using 12/31/9999 in a date field

| This is a perfect case of a lopsided index if the column is indexed. It
| would result in a huge number of gaps in the leaf blocks as the records
| were updated to a valid date value. I would never recommend this.

Received on Thu Dec 19 2013 - 08:57:53 CET

Original text of this message