From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Jean-Yves F(dot) Barbier" <12ukwn(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: seeking advices for function |
Date: | 2011-06-22 21:27:39 |
Message-ID: | BANLkTi=xGq3=k+YH3SGqk3MVwrBr-U1WLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Wed, Jun 22, 2011 at 3:45 PM, Jean-Yves F. Barbier <12ukwn(at)gmail(dot)com> wrote:
> On Wed, 22 Jun 2011 15:07:16 -0500, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>
> ...
>>
>> I think it's much better to use the database log to record security
>> violations.
>
> Ok, so I suppose I have to use such a program as pg_fouine (or even just a
> script with greps) and email results to the DBA.
>
>> Wrapping SQL with a function like this is going to be a
>> problem factory. For example, it's a total optimization fence if you
>> ever need to do something like join against your 'view'. IMO, it's a
>> total non-starter.
>
> This function is to be used against only one table; for joined queries,
> I intend to use the same kind of function, however involving all needed tables.
>
> The goal is (if possible) eliminate views because if I've got 200 user
> profiles, I'll be obliged to generate 200 x (many)viewS.
why in the world do you need to create one view/user/table? that is
absolutely something you would want to avoid...
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Yves F. Barbier | 2011-06-22 21:55:29 | Re: seeking advices for function |
Previous Message | Jean-Yves F. Barbier | 2011-06-22 20:45:26 | Re: seeking advices for function |