On Thu, Apr 01, 2004 at 22:50:48 -0500,
John DeSoi <jd@icx.net> wrote:
>
> Comments/criticisms about design or performance issues?
Except for SQL functions which can be inlined, the optimizer can't
optimize what is being done in the function with what is being done
in the select statement. This might be a performance issue depending
on your particular circumstances.
> Is there a way to provide column security without creating different
> views for every possible scenario?
You should be able to have one view per table and use an OR in the where
clause to check for student, teacher or parent access. These tests
should be simple enough, that you should be able to just do the joins
in the view.
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
