Re: Tool to ease development of plpgsql
От | Dean Arnold |
---|---|
Тема | Re: Tool to ease development of plpgsql |
Дата | |
Msg-id | WtAOb.2897$214.1082@newssvr29.news.prodigy.com обсуждение исходный текст |
Ответ на | Tool to ease development of plpgsql (<bill.postgresql-users@mcmilleon.com>) |
Список | 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@archonet.com> wrote in message news:200401181512.22916.dev@archonet.com... > On Friday 16 January 2004 22:52, bill.postgresql-users@mcmilleon.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 >
В списке pgsql-general по дате отправления: