| From: | Bruno Baguette <bruno(dot)baguette(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Adding ACL notion to existing tables |
| Date: | 2009-08-12 12:30:33 |
| Message-ID: | h5ucl5$11be$1@news.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 08/08/09 02:13, Bruno Baguette a écrit :
> As you can see, I'm not really convinced for SOLUTION A or SOLUTION B as
> they have both some CONS. And they will both require some stored
> procedures to check references integrity. Solution B seems to be less
> weird to me.
>
> What would you do in that kind of situation ? Which solution would you
> take ? Would you uses another design to solve that problem ?
>
> Feel free to leave your appreciation about that problem. Your advices,
> tips or some interesting URLs are welcome also !
No opinion about theses 2 solutions ?
:-/
Many thanks in advance for any advices !
Regards,
--
Bruno Baguette
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-12 13:48:53 | Re: Best way to "mask" password in DBLINK |
| Previous Message | Sam Mason | 2009-08-12 11:47:08 | Re: comparing NEW and OLD (any good this way?) |