> > ERROR: No such function 'datetime' with the specified attributes
> Apparently the datetime() function got renamed to timestamp() in the
> recent consolidation of date/time types. I'd actually recommend that
> you write CURRENT_TIMESTAMP, which is the SQL-approved notation...
> although here also I think now() or CURRENT_TIMESTAMP would be safer
> coding.
Right. We stayed away from recommending anything to do with
"timestamp" in the past because it was such a brain-damaged
implementation.
Sorry for the porting effort; I could imagine someone working on a
"datetime compatibility package" which would define some of these
older functions. It would not need any compiled code, just a set of
CREATE FUNCTION definitions to hook up the new code with the old
names, something possible with Tom Lane's decoupling of entry points
from names...
If you are interested in doing this Oleg I'm sure we could slip it
into the beta tarball...
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California