Re: [Phpwebsite-developers] Table Naming Conventions and Multiple Instances of phpWebSite

[Todd O. <to...@da...>]

I agree multiple phpWebSites should run in one database, but I _disagree_
with the proposed fix.

I am with Aaron and Jason; the sites need to share common tables.  The
following is an excerpt from a March 6th post to the list.

__Multiple Organizations
If we want to make phpWebSite scale to have multiple organizations in the
same database, then we need to add an additional field to each table such as
"ouid" (organizational unit id) ["oid" is reserved for object id in
Postgres].  The primary key for each table would need to be changed to (cid,
ouid) instead of (cid) alone.  To prevent ouid guessing or spoofing, the
user access control list (ACL) would have to be consulted for each page
access, which should be done anyway.

Since this change affects just about every call to the database tables, it
seems to be a good time to add the database abstraction layer while we're at
it.  Will it be PEAR of ADODB?

--Todd