Lists: | pgsql-hackers |
---|
From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | todo: plpgsql - tool to track code coverage |
Date: | 2010-11-05 07:25:46 |
Message-ID: | AANLkTinaLjvmyR42kQbEurw0=W7ZR+=6zXei9agk+p40@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Hello
I am looking on http://kputnam.github.com/piggly/ site. I am thinking,
so can be very easy write low level support to plpgsql. And this can
to solve a some issue of plpgsql with lazy SQL full checking.
A raising syntax error of some SQL inside plpgsql after a months of
production usage is still problem. This or similar tool can minimalize
risks.
Regards
Pavel Stehule
From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: todo: plpgsql - tool to track code coverage |
Date: | 2010-11-05 09:37:06 |
Message-ID: | AANLkTin_AO1Hb6TpUqXc+8PVndsBHy0XhZGiGfWBjtQk@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
2010/11/5 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hello
>
> I am looking on http://kputnam.github.com/piggly/ site. I am thinking,
> so can be very easy write low level support to plpgsql. And this can
> to solve a some issue of plpgsql with lazy SQL full checking.
>
> A raising syntax error of some SQL inside plpgsql after a months of
> production usage is still problem. This or similar tool can minimalize
> risks.
Yes, this is interesting.
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support