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

[Jason C. <cam...@xp...>]

I remember that post about it too now that your brought it up.  Its a very 
good idea to get phpwebsite to be scalable but its bigger than changing one 
thing in the config, it would be better to do what Todd quoted from the 
other message about this option.  I'd be willing to work on it with whoever 
would want to do this on the dev team.

I remember someone saying a new version of ADODB was released, before we 
use one or the other I think we'd have to know how stable each are and 
which one is more widely used by other developers.  Did this get discussed 
anymore on which one to use, PEAR of ADODB???

Jason Campbell
Xplozive Media Technologies
phpWebSite Developer

> 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
> 
> 
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers