in reply to MySQL Database

Here's one reason not to have separate MySQL logins for each user: persistent database connections. Using mod_perl or FastCGI, you can improve performance of an application by keeping persistent connections to the database server. If you only have one database login, you only need one connection per process. If you have multiple logins, you need one connection per login per process. That can add up fast and swamp your database.

Make the right architectural choice now and you will save yorself a lot of hassle later on.

Replies are listed 'Best First'.
Re: Re: MySQL Database
by Anonymous Monk on Mar 04, 2002 at 06:18 UTC
    There's really very little speed improvement in using Apache::DBI for persistent connections to MySQL. My own benchmarking never demonstrated any notable improvement from simple non-persistent connections.
      There's definitely some improvement, since there is less work to be done when you have a persistent connection. It also leaves the door open for switching to another database at some point down the road.