From: | David Johnston <polobo(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | SQL Normalization Thought |
Date: | 2012-03-07 12:34:08 |
Message-ID: | 88AB61BC-ABBF-4FA4-A7A6-A1EAE985F5AF@yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I know there is currently work ongoing regarding normalizing SQL statements for logging purposes but has anyone considered given us the ability to name our statements.
SELECT ....
FROM ...
WHERE ....
NAMEAS 'Name to track by'
If a query lacks a name the algorithm generated normalized form would be used instead but otherwise all queries with the same name would be treated as being the same for statistics purposes.
I'm sure there is more to it but the idea of letting the user name their queries, and thus have something to actually link the logs and the source code directly, has merit and at the least provides a workaround to an algorithmic routine.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | mdione.ext | 2012-03-07 13:10:50 | Re: ERROR: could not find tuple for trigger 37463634 |
Previous Message | Martin Gregorie | 2012-03-07 11:55:40 | Re: Complex transactions without using plPgSQL Functions. It is possible? |