On Tue, 2002-02-19 at 00:46, Gregory Junker wrote: > For reasons of the end-arounds you note it really has to be in the > server. As mentioned views are a possibility, but could end up being > just as messy as a middle tier. It sounds like what you want is > integrated (with the OS) security (as in MS SQL); I don't know if this > is on the plate, but I'm sure it could be done in a future version. :)
Even with MS SQL you have to use views or stored procedures to implement row-level security within the DB itself (aside from splitting the data into different tables or databases for each 'access level'). Given his concern over direct connections sidestepping his security model, he will either have to split the data into seperate tables or databases, or wait for views, so far as I know. I've implemented this (on MS SQL, in fact) via SPs and views in a single database, and it is definitely not a lot of fun if you have a large, complex, heavily normalized DB. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
