Date: Thu, 10 Nov 2005 12:22:39 -0700
From: Michael Fuhr <mike@fuhr.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Rod Taylor <pg@rbt.ca>,
	Judith Altamirano Figueroa <jaltamirano@correolux.com.mx>,
	pgsql-sql@postgresql.org
Subject: Re: time
Message-ID: <20051110192239.GA60396@winnie.fuhr.org>
References: <1131635035.3529.143.camel@Desarrollo>
	<1131646287.819.144.camel@home>
	<20051110182139.GA87715@winnie.fuhr.org>
	<11040.1131650023@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <11040.1131650023@sss.pgh.pa.us>

On Thu, Nov 10, 2005 at 02:13:43PM -0500, Tom Lane wrote:
> Michael Fuhr <mike@fuhr.org> writes:
> > Am I missing something?  Is there a reason not to simply cast the
> > timestamp value to time?
> 
> I think the OP was trying to use the functional cast syntax
> 	time(now())
> which worked long ago, but has not since we added the
> SQL-spec time precision syntax.

I was referring to the expression that Rod Taylor posted, wondering
if there was some subtlety I was missing or if Rod simply didn't
think of the simpler solution (Rod responded indicating the latter).

-- 
Michael Fuhr