Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f28Fisx44006 for ; Thu, 8 Mar 2001 10:44:54 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f28Fic925735; Thu, 8 Mar 2001 10:44:38 -0500 (EST) To: Christopher Sawtell cc: pgsql-sql@postgresql.org Subject: Re: Buglet? In-reply-to: <01030819162000.25266@berty> References: <01030819162000.25266@berty> Comments: In-reply-to Christopher Sawtell message dated "Thu, 08 Mar 2001 19:16:20 +1300" Date: Thu, 08 Mar 2001 10:44:37 -0500 Message-ID: <25732.984066277@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/173 X-Sequence-Number: 1826 Christopher Sawtell writes: > It that a bug? You could argue that. The handling of NULL arrays (not to mention NULLs in arrays) is pretty brain-d^H^H^H^H^H^Hsimplistic; I don't think the original designer thought about NULLs at all. All of the array code could use an overhaul, actually, to move it out of the student-project category and into the professional-tool category. I've taken occasional swipes at it over the past couple of years, but it still leaves a lot to be desired. Any volunteers out there? regards, tom lane