From: | dennis jenkins <dennis(dot)jenkins(dot)75(at)gmail(dot)com> |
---|---|
To: | David Johnston <polobo(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SQL Normalization Thought |
Date: | 2012-03-07 14:03:38 |
Message-ID: | CAAEzAp9n3bDyOYV=o6L-d9pKcJVzjedbaw_DusqfxSZA5HhGKw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Mar 7, 2012 at 6:34 AM, David Johnston <polobo(at)yahoo(dot)com> wrote:
> 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.
>
You could place a 'C style' comment at the beginning of the statement. Ex:
/* MagicQuery-001 */ select awsome_stuff from coolness_table where user_id=?;
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Gregorie | 2012-03-07 14:23:42 | Fixing the loss of 'template1' |
Previous Message | mdione.ext | 2012-03-07 13:10:50 | Re: ERROR: could not find tuple for trigger 37463634 |