> > Yes it does, for ambiguous cases such as yours.
> Which means that independent of the date style, it should give a date error
> either way?
No, it means that for ambiguous cases (e.g. '2-10-1997') it will assume
European or US conventions were used. It will rarely reject a date on
grounds of
Philip Warner <[EMAIL PROTECTED]> writes:
>> SELECT min(id) FROM test; uses sequential scan even if an index on "id"
>> exists. VACUUM ANALYZE doesn't help.
> This is a known stupidity of PG, and will probably be fixed in a relatively
> distant future release (when index entries are updated to ma
At 09:08 2/05/01 -0400, [EMAIL PROTECTED] wrote:
>SELECT min(id) FROM test; uses sequential scan even if an index on "id"
exists. VACUUM ANALYZE doesn't help.
>
This is a known stupidity of PG, and will probably be fixed in a relatively
distant future release (when index entries are updated to ma
> Yes it does, for ambiguous cases such as yours.
Which means that independent of the date style, it should give a date error
either way?
> I'm willing to bet that the date style is *not* set to "European".
> Please demonstrate with a "show datestyle" and "select date
> '2.10.1997'"...
NOTICE: Da
Nick Gazaloff ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
SELECT min(id) FROM test; uses seqscan
Long Description
SELECT min(id) FROM test; uses sequential scan even if an index on "id" exists. VACUUM
ANALYZE doesn't help.
