suggestion: fix 'now' -> CURRENT_TIMESTAMP - Mailing list pgsql-bugs

From Mark Stosberg
Subject suggestion: fix 'now' -> CURRENT_TIMESTAMP
Date
Msg-id slrndj84v7.9sp.mark@simba.summersault.com
Whole thread Raw
Responses Re: suggestion: fix 'now' -> CURRENT_TIMESTAMP  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hello,

I'm in the process of migrating dozens of databases from 7.1 to 8.0.
It's been a great opportunity to become familiar with all the things
that have changed in the meantime.

Of of those things is the meaning 'now', as documented in the 7.4
release notes:
http://www.postgresql.org/docs/8.0/interactive/release-7-4.html
( Search for 'now' on the page to find the related docs. ).

When dumping from 7.1 and restoring into 8.0, working code is being
created in the cases I'm looking at, because these construct is put in
the dump file, and then imported verbatim:

  date("timestamp"('now'::text))
  "timestamp"('now'::text)

This these mean the exact same thing as:

    CURRENT_DATE
    CURRENT_TIMESTAMP

( But not the same thing as a bare 'now' ).

Why not make the translation on the fly, since using 'now' and
timestamp() are not recommended practices anyway ?

I have seen that PostgreSQL has already taken the liberty to rewrite
"serial" and other schema constructions when they are dumped or
imported, so I see no problem with rewriting code to equivalent, but
better style.

For now I'm doing find & replace on the dump files as a workaround.

    Mark

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #1850: parameter WITH HOLD (of function DECLARE CURSOR)
Next
From: Tom Lane
Date:
Subject: Re: suggestion: fix 'now' -> CURRENT_TIMESTAMP