From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org, jm(dot)poure(at)freesurf(dot)fr, Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Subject: | Re: Timestamp reverse engeneering bug |
Date: | 2002-02-21 19:04:54 |
Message-ID: | ZTXY9JNw63gt.HqCkFHv1@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
I'm using my phone right now so I can't check, but I'm pretty sure that's not a bug. Isn't timestamptz a timestamp with timezone e.g. 2002-02-21 19:00:00+00?
Anyway, pgAdmin gets this by looking up the typename from pg_type using pg_attribute.atttypid (iirc) so if it's broken for one type it probably would be for all types.
I'll check when I can...
Regards, Dave
_____________Original message ____________
Subject: [pgadmin-hackers] Timestamp reverse engeneering bug
Sender: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
Date: Thu, 21 Feb 2002 18:57:05 +0000
Hi Dave,
Table definition with timestamps under 7.2 return "timestamptz".
Cheers,
Jean-Michel POURE
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-02-21 20:08:01 | Re: Timestamp reverse engeneering bug |
Previous Message | Jean-Michel POURE | 2002-02-21 18:44:43 | Timestamp reverse engeneering bug |