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

From: TJ Kiernan <tkiernan_at_pti-nps.com>
Date: Wed, 18 Dec 2013 16:04:08 +0000
Message-ID: <196DB2D4BDE5804EAF3158CCC1C698BC09B3D24A_at_lopez.pti-nps.com>



As recently as last year's Hotsos Symposium, Mr. Kyte recommended against it. If this developer is not blowing smoke, it is a very recent change in position, and likely only applies to 12c and beyond. IIRC, there are some changes to histograms in 12c, but I don't recall specifically if bad/false defaults instead of null values were addressed.

If it were me, I'd demand some links from the developer so some context can be applied.

Thanks,
T. J.

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jay.Miller_at_tdameritrade.com Sent: Wednesday, December 18, 2013 9:53 AM To: oracle-l_at_freelists.org
Subject: Using 12/31/9999 in a date field

I've always told people to avoid this like the plague but I'm now on a call with a developer who says Oracle in general and Tom Kyte specifically have changed their position on this and they now recommend it.

Has anyone heard anything about this or have a white paper or link that I can review? Or if it still isn't a good idea (I have a hard time imagining it is but maybe the optimizer has gotten a lot smarter) have a link showing the opposite more recent than the 2008 Tom Kyte article?

Thanks!

Jay Miller

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Dec 18 2013 - 17:04:08 CET

Original text of this message