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.
