piggly
piggly copied to clipboard
PL/pgSQL stored procedure code coverage tool
Stored procedure written using CREATE PROCEDURE are not working. Why trying to trace it gives error - "DETAIL: "total_score" is a procedure." 1. Is there anyone facing the same error?...
This is an old project, it's meant to be a simple and utilitarian: do one thing and do it okay enough. However the UI has always been ugly, even by...
Since I no longer write PL/pgSQL during the course of my work, it takes me some time to setup a test environment when making changes to this project. Now that...
A function which declares a bigint is throwing an error when executing the trace command. Env: Docker postgres:12.1-alpine Extract from problematic function `CREATE OR REPLACE FUNCTION test.piggly ( param1 INT...
A function that looks like this: ``` create or replace function foo() returns void language plpgsql as $$ DECLARE DECLARE mycur CURSOR FOR SELECT * from pg_database; BEGIN return; END;...
The current method of replacing an existing function with an instrumented uses `CREATE OR REPLACE FUNCTION`. Since we don't save all the metadata like `COST` or other attributes, those can...
Hi, I'm very interested in this library, but I would like to integrate it into existing code coverage tools. Is there any way to export the code coverage to an...
IF (CASE WHEN x IS NULL THEN FALSE WHEN x = 'abc' THEN FALSE ELSE TRUE END) THEN RAISE EXCEPTION 'error message'; END IF; The parser seem to have issues...
The parser incorrectly requires a space before `THEN`. But PostgreSQL accepts `IF(cond)THEN`, because there's a parenthesis to separate the keyword. The grammar node that needs to change is `expressiontUntilThen`. There...