Re: [Phpwebsite-developers] New version and Roadmap [long]

[Benji S. <bsp...@mo...>]

Before I start, I would like to give a little background as to what we are 
looking to use phpWebsite for.

We are an educational institute that is looking to use a CMS for the 
various internal departments. We have the typical educational areas like 
Undergraduate, Student Development, Graduate, and Admissions, but we also 
have 15 radio stations (and other various radio programs), a magazine, 
retail operations, and other areas that we want to migrate to a CMS. Our 
needs differ from those of an ISP. We have a number of clients, but they 
all are internal clients.

Because of that, the number of db's vs. number of tables issue isn't a big 
one. Each content area will have its own CMS installation (be it under the 
current phpWebsite, with one installation per content area, or under the 
future phpWebsite, which can handle multiple OUs under one umbrella). A 
bigger question for us would be which option is a better use of the 
database and which is better from a management standpoint? If there any 
performance difference between having a number of databases, with a number 
of tables in each, or having one database, with lots of tables in?

Which is better from the php standpoint? Would the connection load (via 
pconnect) be less if everything was in database?

Which would make management easier?

just some thoughts from non-ISP side.

benji


---
Ben Spencer
Web Support
bsp...@mo...
x 2288