They code in a personal and integrate into a central development schema. Can
we avoid public synonyms in this case?
That was my question.
"Andy Hassall" <andy_at_andyh.co.uk> wrote in message
news:v3tiv0p6epglk8409fp1tc14tg3spvmhbo_at_4ax.com...
> On Wed, 26 Jan 2005 20:29:02 -0500, "Oradba Linux"
<techiey2k3_at_comcast.net>
> wrote:
>
> >How to really use the alter session set current_schema='APPUSERID' in a
devl
> >env for a set of 20+ developers ?
>
> Fairly ambiguous question, but making a number of assumptions:
>
> * each developer has their own Oracle account
> * they only have read access, or carefully regulated write access (e.g.
> through APIs not owned by their user account)
>
> ... then one approach is with an AFTER LOGON trigger on each of their
user
> accounts.
>
> If they have write access and are actively developing the APIs to
> create/modify data, then shouldn't they have their own separate
application
> data schema/schemata to mess with? In which case the after logon trigger
may
> still apply, but would alter session to point to a separate schema per
> developer rather than a central development schema.
>
> --
> Andy Hassall / <andy@andyh.co.uk> / <http://www.andyh.co.uk>
> <http://www.andyhsoftware.co.uk/space> Space: disk usage analysis tool
Received on Fri Jan 28 2005 - 18:38:50 CST
