| From: | Jorge Godoy <jgodoy(at)gmail(dot)com> |
|---|---|
| To: | Shane Ambler <pgsql(at)007Marketing(dot)com> |
| Cc: | snacktime <snacktime(at)gmail(dot)com>, PostgreSQL Mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: using schema's for data separation |
| Date: | 2006-09-29 14:20:38 |
| Message-ID: | 87k63mbvpl.fsf@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Shane Ambler <pgsql(at)007Marketing(dot)com> writes:
> Thinking about it - it should only be a small source change to the sql
> parser to stop it from running a statement that didn't include clientID in
> the where clause.
> A small change that is easy to add again to new versions as they are
> released.
I'd avoid modifying source code and go with either a function or view. All
queries should be against those and they'd fail if the id is missing. All
filtered tables should have an index on such id, of course...
--
Jorge Godoy <jgodoy(at)gmail(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | km | 2006-09-29 14:28:01 | Re: benchmark suite |
| Previous Message | Shane Ambler | 2006-09-29 14:10:39 | Re: using schema's for data separation |