Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 34C276327A3 for ; Thu, 19 Feb 2009 06:21:48 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 06421-03 for ; Thu, 19 Feb 2009 06:21:38 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.morphoss.com (hoppy.mcmillan.net.nz [202.78.240.82]) by mail.postgresql.org (Postfix) with ESMTP id 1BDE8632504 for ; Thu, 19 Feb 2009 06:21:38 -0400 (AST) Received: from [192.168.55.195] (218-101-8-114.xtreme.net.nz [218.101.8.114]) (Authenticated sender: andrew@mail.morphoss.com) by mail.morphoss.com (Postfix) with ESMTPSA id 6B1432309F; Thu, 19 Feb 2009 23:21:29 +1300 (NZDT) Subject: Re: pl/php for windows From: Andrew McMillan To: "Rodrigo E. De" =?ISO-8859-1?Q?Le=F3n?= Plicet Cc: pgsql-php@postgresql.org In-Reply-To: (sfid-20090219_193434_592021_623DC99E) References: <873a98c60902180641u2320846bq4261bde13d59dd7a@mail.gmail.com> <499CAA23.3050504@lightlink.com> <1235005446.22166.31.camel@happy.mcmillan.net.nz> <499CCC25.80200@lightlink.com> (sfid-20090219_193434_592021_623DC99E) Content-Type: text/plain; charset=UTF-8 Date: Thu, 19 Feb 2009 23:21:28 +1300 Message-Id: <1235038888.22166.48.camel@happy.mcmillan.net.nz> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/13 X-Sequence-Number: 3989 On Thu, 2009-02-19 at 01:34 -0500, Rodrigo E. De León Plicet wrote: > On Wed, Feb 18, 2009 at 10:04 PM, Bob McConnell wrote: > > (...) we have a company policy forbidding stored procedures (...) > > Why would that be? > > Just curious... I can't speak for Bob, and they probably have different reasons, but personally I almost always only write stored procedures in SQL or PL/PgSQL, and I think very hard about it before deciding to do so, and try and be careful to design to a minimal functionality that can then be used in normal SQL. There can be memory effects from loading a large interpreter into a PostgreSQL client, which can cause pain if you have many connections, but mostly I don't trust the software versions to become wildly out of sync and multiply the installation & maintenance complexity. PostgreSQL also can have some problems planning queries containing functions. ... that said, I *have* written a set of functions in PL/PgSQL for parsing iCalendar RRULE + DTSTART into a SETOF TIMESTAMP. Just purely for giggles, of course :-) Cheers, Andrew. PS. In a past life I was responsible for maintaining an application written entirely in Oracle's PL/SQL. I don't ever want to repeat that, so that probably imposes a bias of sorts too! ------------------------------------------------------------------------ andrew (AT) morphoss (DOT) com +64(272)DEBIAN You never hesitate to tackle the most difficult problems. ------------------------------------------------------------------------