Shane Ambler <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
