Yes, that's what I want. For me, this is a good idea since you have the following advantages: - Restrict users to certain tables and columns on a database level instead on application level providing security in case a user circumvents the application level security. - No duplication of authentication/ACL functionality - Possibility to use all kinds of functionality in the database using PL/pgSQL with regards to storing record-changes in subtables, timestamps and other user/security related stuff - Possibility for accessing the database with other frontends (like MS Access using ODBC) without needing to duplicate authentication code/ functionality in those front-ends - If you use a general database user, you give them more permissions in a database server then when using separate users
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
