From: | Christopher Weimann <csw(at)k12hq(dot)com> |
---|---|
To: | Andrus Moor <eetasoft(at)online(dot)ee> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Wish: remove ancient constructs from Postgres |
Date: | 2006-02-27 22:56:32 |
Message-ID: | 20060227225632.GB98075@tektite.k12usa.internal |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/26/2006-10:36AM, Andrus Moor wrote:
>
> It is difficult to write standard-compliant code in Postgres.
> There are a lot of constructs which have SQL equivalents but are still used
> widely, even in samples in docs!
>
> For example, there are suggestions using
>
> now()::CHAR!=foo
>
> while the correct way is
>
> CAST(CURRENT_DATE AS CHAR)<>foo
>
> now() function, :: and != operators should be removed from language.
>
> I like the Python logic: there is one way
Actually the python logic is
"There should be one-- and preferably only one --obvious way to do it."
Perhaps the suggestion should be to only use the SQL standard forms in
the documentation, making them the 'obvious' way.
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2006-02-28 00:36:17 | In case nobody has seen this survey from Sun ... |
Previous Message | Jebus | 2006-02-27 22:12:44 | audit tables adding columns |