| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> | 
|---|---|
| To: | "Alessio Bragadini" <alessio(at)albourne(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: Display of TIMESTAMP in 7.2 | 
| Date: | 2002-02-06 02:03:21 | 
| Message-ID: | GNELIHDDFBOCMGBFGEFOIEEJCBAA.chriskl@familyhealth.com.au | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Try using CURRENT_TIMESTAMP instead of now() maybe?
Chris
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Alessio
> Bragadini
> Sent: Tuesday, 5 February 2002 8:19 PM
> To: PostgreSQL Hackers
> Subject: [HACKERS] Display of TIMESTAMP in 7.2
> 
> 
> Hi all,
> starting with 7.2, now() returns a time with milliseconds. If extracted
> from the db and displayed verbatim, it shows up as
> '2002-02-05 10:59:36.717176+02'.
> 
> Unfortunately, I have a lot of code that displays the date/time directly
> from the db on a web page without any to_char transformation and now
> that is quite harder to understand. Is there any way to have an implicit
> formatting back that trims the milliseconds on a per-connection
> variable?
> 
> -- 
> Alessio F. Bragadini		alessio(at)albourne(dot)com
> APL Financial Services		http://village.albourne.com
> Nicosia, Cyprus		 	phone: +357-22-755750
> 
> "It is more complicated than you think"
> 		-- The Eighth Networking Truth from RFC 1925
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
> 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2002-02-06 02:30:45 | Re: single task postgresql | 
| Previous Message | Christopher Kings-Lynne | 2002-02-06 01:56:42 | installing client without server |