Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by postgresql.org (Postfix) with ESMTP id ADD11475928 for ; Sat, 23 Feb 2002 16:37:43 -0500 (EST) Received: from there (202-0-37-152.cable.paradise.net.nz [202.0.37.152]) by deborah.paradise.net.nz (Postfix) with SMTP id 78D43D26F2; Sun, 24 Feb 2002 10:37:42 +1300 (NZDT) Content-Type: text/plain; charset="iso-8859-1" From: Christopher Sawtell Reply-To: csawtell@paradise.net.nz Organization: Chez Moi To: Rajesh Kumar Mallah , pgsql-sql@postgresql.org Subject: Re: should I use postgresql arrays... Date: Sun, 24 Feb 2002 10:32:12 +1300 X-Mailer: KMail [version 1.3.1] References: <3C7738A7.78485275@trade-india.com> In-Reply-To: <3C7738A7.78485275@trade-india.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020223213743.78D43D26F2@deborah.paradise.net.nz> X-Archive-Number: 200202/344 X-Sequence-Number: 6766 On Saturday 23 February 2002 07:37 pm, Rajesh Kumar Mallah wrote: > Hi folks, > > Using Postgresql array feature can siplify > lot of coding in my application layer as well as > database design , for example for storing checkbox > selections in a web page i need not have a > secondary table referencing the master one. > > should i be using arrays for that? It all depends, I have found array operations to be slow. So if you have just a few elements, like less than 10 then arrays are ok, but with more e.g. 30+ elements, as in my case, imho the whole exercise is not really feasable. I am going to re-design the schema to get rid of the arrays as soon as I have a moment. Also the code around that part of PostgreSQL has not been visited for a fair while and needs some polishing up. I'd avoid them. > My only concern is the SQL compliance , are arrays > part of standard 2/3 standards? > > what if at a later date i decide to migrate my database > to another engine. You will need to do a fair amount of work to get rid of them. -- Sincerely etc., Christopher Sawtell