Nuno Souto wrote:
>
> Have been doing extensive design and PL/SQL API development for a J2EE
> front end. One set of tables are used globally, others are specific
> to each sub-system. In all nearly 200 tables.
>
> I've got the global ones in one schema, the others each on its schema.
> A "wrapper" schema then concentrates all the API procedures and
> packages that access the required schemas as needed, with appropriate
> security established.
>
> A Java "guru" the other day asked in a very "suspicious" way if that
> was a " *normal* ORACLE design process", to have "multiple schemas in
> a database, one for each subsystem".
>
> Please tell me I'm not dreaming: the guy is a nong, right?
>
> Sometimes I doubt if I'm living in the same world...
>
> Ah, yes!: 8.1.7, M$ NT4
> TIA
>
> Cheers
> Nuno Souto
> nsouto_at_optushome.com.au.nospam
I don't know if he is wrong. I have always modeled different functions
of applications into different schemas. It is analogous to writing Java
classes vs. one BIG program.
--
Ron Reidy
Oracle DBA
Received on Wed Dec 19 2001 - 05:50:26 CST
