X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 27D87D1CB03 for ; Mon, 3 Nov 2003 14:58:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 75959-05 for ; Mon, 3 Nov 2003 10:58:22 -0400 (AST) Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id 37750D1B523 for ; Mon, 3 Nov 2003 10:58:12 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by ucsns.ucs.co.za (Postfix) with ESMTP id D02D42BDC8 for ; Mon, 3 Nov 2003 16:58:10 +0200 (SAST) Received: from ucsns.ucs.co.za ([127.0.0.1]) by localhost (ucsns.ucs.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23645-02 for ; Mon, 3 Nov 2003 16:58:09 +0200 (SAST) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id E55662BDB3 for ; Mon, 3 Nov 2003 16:58:09 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id E4A68DA9D5 for ; Mon, 3 Nov 2003 16:58:09 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with SMTP id 1109A976E9 for ; Mon, 3 Nov 2003 16:58:10 +0200 (SAST) Date: Mon, 3 Nov 2003 16:58:04 +0200 From: Stef To: pgsql-sql@postgresql.org Subject: 'invalid' value in timestamp with timezone. Message-Id: <20031103165804.4aab8385.svb@ucs.co.za> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: LV^-*d3kQlL,6{Y:X)M~tuL#y!p.kO_Qbc!xxqhZC4s}Y]L0g)z^aiLsQGY34d|}Xp:HNm)MRsc?^?ZQ}smznF&jx|w@,a**K&QL.Dc~2~M5V`zb>hExCJDB[[o=M)e"; k-n[7tz2TY7+; *_xX's(5cUEtdw*yG-OmKm}6($zpUz8S`Nz@w X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Mon__3_Nov_2003_16_58_04_+0200_MJc.SC4PEKUHgo7G" X-Virus-Scanned: by amavisd-new at ucs.co.za X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/11 X-Sequence-Number: 15826 --Signature=_Mon__3_Nov_2003_16_58_04_+0200_MJc.SC4PEKUHgo7G Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi all, I've noticed for the first time in some 7.1.2 databases that I use, that somebody/something managed to insert a literal alpha value of 'invalid' into 'timestamp with timezone' columns. I tested it myself, and it worked : test712=# create table bob (field timestamp); CREATE test712=# \d bob Table "bob" Attribute | Type | Modifier -----------+--------------------------+---------- field | timestamp with time zone | test712=# insert into bob values('invalid'); INSERT 3885934 1 On 7.3.4 it gives me : test734=> insert into bob2 values('invalid'); ERROR: TIMESTAMP WITH TIME ZONE 'invalid' no longer supported but other strings gave me the same error on both db's : test734=> insert into bob2 values('valid'); ERROR: Bad timestamp external representation 'valid' I looked in the documentation and on the net, but cannot find much reference to this "ex-feature" I'm 80% sure no one actually inserted these 'invalid' values into tables, and what I need to know is : What else can insert a value of 'invalid' into a 7.1.2 "timestamp with timezone" type column. Was there a function or something similar? Regards Stef --Signature=_Mon__3_Nov_2003_16_58_04_+0200_MJc.SC4PEKUHgo7G Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/pm0CgDYs3UkRjZkRAkrhAJ9kVq7mxBlJHR9zG5JZB6eKfxrs7wCfeq8X yyOkikEruQLIZS6/d/9CVL4= =cZKz -----END PGP SIGNATURE----- --Signature=_Mon__3_Nov_2003_16_58_04_+0200_MJc.SC4PEKUHgo7G--