Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 3BA799FB2B8; Fri, 29 Sep 2006 14:37:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 38581-01; Fri, 29 Sep 2006 17:37:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from myemma.com (db1.e2ma.net [66.179.147.163]) by postgresql.org (Postfix) with ESMTP id 8B77B9FB292; Fri, 29 Sep 2006 14:37:33 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by myemma.com (Postfix) with ESMTP id 69D1C23CDC; Fri, 29 Sep 2006 12:37:32 -0500 (CDT) Received: from myemma.com ([127.0.0.1]) by localhost (velma [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13611-04; Fri, 29 Sep 2006 12:37:32 -0500 (CDT) Received: from [10.0.23.48] (unknown [205.241.239.26]) by myemma.com (Postfix) with ESMTP id A6CD023CEA; Fri, 29 Sep 2006 12:37:31 -0500 (CDT) Message-ID: <451D59DA.7090203@myemma.com> Date: Fri, 29 Sep 2006 12:37:30 -0500 From: Erik Jones User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: "Paul B. Anderson" Cc: pgsql-admin@postgresql.org, pgsql-general@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [GENERAL] Array assignment behavior (was Re: Stored procedure References: <451C48AB.6090508@pnlassociates.com> <9461.1159502232@sss.pgh.pa.us> <451D34FD.3050709@pnlassociates.com> <451D37C8.8060502@pnlassociates.com> <16926.1159546451@sss.pgh.pa.us> <451D52FF.5000602@pnlassociates.com> In-Reply-To: <451D52FF.5000602@pnlassociates.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at myemma.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.133 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/372 X-Sequence-Number: 23286 Yep, that definitely threw me the first time I encountered it. Paul B. Anderson wrote: > It seems that the suggestion to fill intermediate positions with NULLs > would be preferable to the current behavior. > > I know of no requirement to populate arrays in sequence in any other > language so I think other programmers would be surprised too by the > current behavior. > > Paul > > > Tom Lane wrote: >> [ expanding this thread, as it now needs wider discussion ] >> >> "Paul B. Anderson" writes: >> >>> Actually, I was not filling all of the arrays in sequential order. I >>> added code to initialize them in order and the function seems to be >>> working now. Is that a known problem? >>> >> >> Well, it's a documented behavior: section 8.10.4 saith >> >> A stored array value can be enlarged by assigning to an element >> adjacent to those already present, or by assigning to a slice >> that is adjacent to or overlaps the data already present. >> >> Up to 8.2 we didn't have a lot of choice about this, because without any >> ability to have nulls embedded in arrays, there wasn't any sane thing to >> do with the intermediate positions if you assigned to an element not >> adjacent to the existing range. As of 8.2 we could allow assignment to >> arbitrary positions by filling the intermediate positions with nulls. >> The code hasn't actually been changed to allow that, but it's something >> we could consider doing now. >> >> Comments? >> >> regards, tom lane >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 9: In versions below 8.0, the planner will ignore your desire to >> choose an index scan if your joining column's datatypes do not >> match >> >> . >> >> -- erik jones software development emma(r)