> > For reasons beyond my control, a web application > (apache/Tomcat/PostgreSQL) that I support will need to be partitioned > into one context per customer (to support one database per customer). > I'm wondering: >
Do you really need one database per customer? In a similair situation, we resolved this by adding a "client code" to all our database tables & indexes. Each customer/client was given their own URL to access the system and a filter used the incoming url to load a client code into the request headers before passing the request to a single servlet. Regards Roger __________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. __________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
