Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id eA56FBs62795 for ; Sun, 5 Nov 2000 01:15:11 -0500 (EST) (envelope-from pgsql-hackers-owner@postgresql.org) Received: from golem.jpl.nasa.gov (dialin-096.jpl.nasa.gov [128.149.231.96]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA47QRs85316; Sat, 4 Nov 2000 02:26:27 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1]) by golem.jpl.nasa.gov (Postfix) with ESMTP id AE301178D7; Sat, 4 Nov 2000 07:43:19 +0000 (UTC) Message-ID: <3A03BE17.86ACB325@alumni.caltech.edu> Date: Sat, 04 Nov 2000 07:43:19 +0000 From: Thomas Lockhart Organization: Yes X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15-4mdksmp i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane Cc: Frank Joerdens , pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] DBD::Pg installation seems to fail with 7.1 libs References: <20001103143435.A16341@rakete.joerdens.de> <8277.973288548@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200011/189 X-Sequence-Number: 267 > Thomas, you've been muttering about altering the type resolution rules > so that "unknown" will be treated as "text" when all else fails. Are > you planning to commit such a thing for 7.1? If not, I'll probably have > to hack up parse_coerce.c's select_common_type(), along the lines of I'm *finally* getting several patches together, to do the following things: o Fix the type resolution for unknown function arguments to fall back to "text" or a string type, if available. Previously discussed. o Implement an AT TIME ZONE clause, per SQL9x. Will handle an INTERVAL argument, per standard, and also accept a string containing a time zone spec, per existing PostgreSQL extension. Previously discussed. o Fix timestamp/interval math across daylight savings time boundaries. Previously discussed. o Allow interpretation of "hh:mm:ss" as INTERVAL input. I can't remember if I've mentioned this one before. o Fix output of INTERVAL when sign of year/month is different than sign of hour/min/sec. This is accompanied by changes in the "ISO" form of output to more closely resemble a "hh:mm:ss" format. I just noticed the problem today, so have not discussed it on list yet. o Add some JOIN regression tests. More should be and will be done, but I don't want to keep holding back patches on this. Per Tom Lane's request. The only one with some potential for user trouble is the INTERVAL format change. The old code was wrong, but the format itself has been changed to be a little more concise. - Thomas