Received: from sandtstudent.pyr.ec.gc.ca (fwvan1.pyr.ec.gc.ca [199.212.20.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e6AIrIW56964 for ; Mon, 10 Jul 2000 14:53:19 -0400 (EDT) Received: from ec.gc.ca (IDENT:huangb@sandtstudent [131.235.150.249]) by sandtstudent.pyr.ec.gc.ca (8.9.3/8.9.3) with ESMTP id LAA27185 for ; Mon, 10 Jul 2000 11:52:30 -0700 Message-ID: <396A1B6A.E51A5499@ec.gc.ca> Date: Mon, 10 Jul 2000 11:52:26 -0700 From: Bernie Huang Organization: Environment Canada X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: PGSQL-SQL Subject: Timestamp problem Content-Type: multipart/mixed; boundary="------------B643F2E3DEDF1517EF8F5B91" X-Archive-Number: 200007/106 This is a multi-part message in MIME format. --------------B643F2E3DEDF1517EF8F5B91 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Hi, I have Postgres 7.0, and I created a table table --------- ... borrow timestamp return timestamp Now, I thought timestamp is in sec eg; 35434434, but in PostgreSQL, it shows up as datetime datatype eg; 2000-06-07 17:00:05-07. I was wondering is this format a correct one for timestamp, or is it a bug? Abd if I want to show the time, each retrieval I have to chop of the '-07' timezone at the end. Is there a way to avoid this being show up in Postgres? Thanks. - Bernie --------------B643F2E3DEDF1517EF8F5B91 Content-Type: text/x-vcard; charset=iso-8859-15; name="bernie.huang.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Bernie Huang Content-Disposition: attachment; filename="bernie.huang.vcf" begin:vcard n:Huang;Bernie tel;fax:(604)664-9195 tel;work:(604)664-9172 x-mozilla-html:TRUE org:Environment Canada;Standards and Technology Services adr:;;700-1200 West 73 Ave.;Vancouver;BC;V6P 6H9;Canada version:2.1 email;internet:bernie.huang@ec.gc.ca title:Programmer x-mozilla-cpt:;0 fn:Bernie Huang end:vcard --------------B643F2E3DEDF1517EF8F5B91--