On Wed, 24 Jul 2002, Ralph Einfeldt wrote:
> Date: Wed, 24 Jul 2002 09:07:22 +0200
> From: Ralph Einfeldt <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: AW: More flexible JDBCRealm implementation ? (for ASP-style
> webapp)
>
>
> See Below:
>
> > -----Ursprüngliche Nachricht-----
> > Von: Soefara Redzuan [mailto:[EMAIL PROTECTED]]
> > Gesendet: Mittwoch, 24. Juli 2002 08:52
> > An: [EMAIL PROTECTED]
> > Betreff: Re: More flexible JDBCRealm implementation ? (for ASP-style
> > webapp)
> >
> >
> > Yes, but this adds complexity due to different table names
> > for different clients.
>
> With a 'real' database each web application can use the same
> table name. You just must configure the web application to use a
> different schema (catalog, database, ....; the terms differ from
> vendor to vendor)
>
> >
> > I do prefer to share the tables. The reason is that you can easily set
> > up new clients and customers without restarting Tomcat.
> > Better yet, users can register and sign-up themselves, something
> that's
> > not possible if I have to set up a different database for them, with
> > its own JNDI resource configuration in server.xml
>
> <snip/>
>
> > I'll have to investigate this use of views. It's something I'd never
> > considered before and looks very useful.
>
> With mysql you better forget it.
>
> Currently there are no views in mysql. (Altough chances have improve
> that there will be views in a future version. The views have a higher
> priority in the todo list than 2 years ago)
>
In the open source database world, Postgres has views that are quite
effective for adapting existing table structures to what JDBCRealm
requires.
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
