Idea :
Create a function with the same name as your function, but which takes a
timestamp as an argument, converts it to a string according to your
specifications, then calls your function which needs a string.
Postgresql will decide which function to call according to the types of
the
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> ... I'd like to know
> if there is a specific reason there's no default timestamp -> varchar
> cast.
There is an explicit cast from timestamp to varchar, at least in recent
releases:
regression=# select 'now'::timestamp::varchar;
varchar
