Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA16106 for ; Tue, 14 Sep 1999 11:49:24 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA16626; Tue, 14 Sep 1999 11:45:54 -0400 (EDT) To: Michael Richards cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Array Madness In-reply-to: Your message of Tue, 14 Sep 1999 12:42:53 -0300 (ADT) Date: Tue, 14 Sep 1999 11:45:54 -0400 Message-ID: <16624.937323954@sss.pgh.pa.us> From: Tom Lane Michael Richards writes: > On Tue, 14 Sep 1999, Tom Lane wrote: >> In the meantime, perhaps it would be better for ExecEvalArrayRef() to >> raise an error if the assign source is null, rather than dropping the >> whole contents of the array. Comments? > This sounds like a hack that avoids the real issue... Well, of course it's not a solution to the real issue, but it seemed like it might prevent someone from accidentally losing data until we get around to providing a real solution. (Which could be a long time; there's a lot of things on the TODO list...) regards, tom lane