[HACKERS] todo: plpgsql - tool to track code coverage

2010-11-05 Thread Pavel Stehule 
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

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] todo: plpgsql - tool to track code coverage

2010-11-05 Thread Cédric Villemain 
2010/11/5 Pavel Stehule pavel.steh...@gmail.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

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers