Schema organization... Best practices...
- From: David Mann <dmann99@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Thu, 4 Oct 2012 16:19:20 -0400
Yes, I cringed when I typed Best Practices... But looking for
something along those lines...
Like many folks on the list I have encountered my share of
applications where Password=Username and it had been that way for a
decade or more. Everyone knew the password, miraculously no one had
ever dropped a table or deleted data they shouldn't have... But there
were no protections. I am helping create an application from the
ground up and certainly have some ideas of how things should be
organized but always like to review prior art for a sanity check.
My search-fu is failing me. I know I have seen discussions on schema
organization before but couldn't seem to scare any up on The Google.
I am thinking best practices to approach the full life cycle of
schemas to support applications along the lines of...
o MYPROJECT_OWNER schema, owns objects and data, account locked unless
for maintenance
o MYPROJECT_READONLY schema, granted SELECT on tables necessary for
operations, option to create SYNONYMS to make access easier or more
transparent
o MYPROJECT_APP schema, granted SELECT/INSERT/UPDATE/DELETE to tables
as necessary for operations, option to create SYNONYMS to make access
easier or more transparent
Any pointers to resources or discussions would be much appreciated.
Regards,
-Dave
--
Dave Mann
General Geekery | www.brainio.us
Database Geekery | www.ba6.us | @ba6dotus | http://www.ba6.us/rss.xml
--
//www.freelists.org/webpage/oracle-l
Other related posts:
- » Schema organization... Best practices... - David Mann
