Re: How does one enter dates beyond the implicit, Oracle internal date limits?
From: Maxim Demenko <mdemenko_at_gmail.com>
Date: Sat, 30 Jan 2010 13:02:08 +0100
Message-ID: <4B641FC0.2020202_at_gmail.com>
I can only guess, the main reason is performance - you have an api where validation is done, but performance is not so good, you have an api with better performance, but without validation (or, better to say, where validation is supposed to be done by client application). Best regards
Date: Sat, 30 Jan 2010 13:02:08 +0100
Message-ID: <4B641FC0.2020202_at_gmail.com>
I can only guess, the main reason is performance - you have an api where validation is done, but performance is not so good, you have an api with better performance, but without validation (or, better to say, where validation is supposed to be done by client application). Best regards
Maxim
On 30.01.2010 12:49, Charles Schultz wrote:
> Thanks, Maxim, that is very interesting. But why does Oracle even
> allow it? I assume the date ranges are typically enforced via some
> kind of internal constraint, and sqlldr bypasses constraints for the
> sake of speed. Is this really a "feature"? =)
>
-- http://www.freelists.org/webpage/oracle-lReceived on Sat Jan 30 2010 - 06:02:08 CST