Re: Tool to ease development of plpgsql

From: "Dean Arnold" <darnold(at)presicient(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Tool to ease development of plpgsql
Date: 2004-01-18 18:44:06
Message-ID: WtAOb.2897$214.1082@newssvr29.news.prodigy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Would a tool like www.presicient.com/teraforge be of value ?
I'm thinking of making a Pg port....if interested, please
let me know, and let me know what kind of features
you'd like to see...

--
Dean Arnold
Presicient Corp.
www.presicient.com

"Richard Huxton" <dev(at)archonet(dot)com> wrote in message
news:200401181512(dot)22916(dot)dev(at)archonet(dot)com(dot)(dot)(dot)
> On Friday 16 January 2004 22:52, bill(dot)postgresql-users(at)mcmilleon(dot)com
wrote:
> > What's the best way to ease development of plpgsql.
> >
> > My largest issues with plpgsql pertain to the quoting of course.
>
> I personally use kate (on KDE) or vi, but any syntax-hightlighting editor
can
> help. I don't use anything fancy, just make sure the highlighting picks up
> quoting / comments.
> Edit the file with your function and use \i from psql to test it - that'll
> give you line numbers for errors too.
> ALWAYS make sure your variables/parameters have names that are different
from
> columns in queries.
>
> Having done a _lot_ of plpgsql in the last few months, what irritates from
my
> end is:
> 1. Can't EXPLAIN inside a function
> 2. Error reporting not always useful
> 3. To work around the EXPLAIN problem I copy/paste SQL from my function,
at
> which time I have to unfix the quoting, then paste it back and refix the
> quoting...
>
> Anyway - there is the possiblilty that something a bit like shell/perl
HERE
> documents might exist in 7.5 which'll make the quoting problem go away.
>
> --
> Richard Huxton
> Archonet Ltd
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2004-01-18 18:56:17 Re: computed field on a table
Previous Message David Garamond 2004-01-18 18:08:35 computed field on a table