On Mon, Oct 09, 2006 at 01:49:37PM -0400, Tom Lane wrote: > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > On Mon, Oct 09, 2006 at 12:02:12PM -0400, Tom Lane wrote: > >> ... I think Jeremy's problem would be solved just by applying > >> the float8 version to "extract(epoch from timestamp)". > > Thinko there ... I meant to type "extract(epoch from interval)".
Except that the patch is for timestamp support, not intervals. > > Well, it would be nice to have a timestamp version so that users didn't > > have to keep typing "extract(epoch from timestamp)"... but yeah, I > > suspect that would work fine for timestamps. For intervals I suspect you > > could just convert to seconds (if we're going to add timestamps, it > > seems like we should add intervals as well). > > This is exactly the slippery slope I don't care to start down. I guess I'm confused as to how this is any different from other functions where we've provided multiple input arguments, such as the aggregate functions. It certainly doesn't seem like it'd take a lot of extra code to support this... -- Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
