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

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

Geoff,

> That means you must rely on the security in phpWebsite to control access
> if you segment by using an organization id (OID) in the tables. (Not that
> there's anything wrong with that.)

My philosophy is consistant with the statement above.  You are correct that
separate tables are the only way to use MySQL database security (row level
security would be a bear anyway).  Your observation that each "site" admin
could dump (and restore) their own tables is a good point.  My "combined"
table scheme would have "super" administrators, like root, that could
create, delete and modify site administrators, back-up data and so forth.
More on this later.

> I agree that having an organizational unit id would be a great idea.
> HOWEVER, that will not happen soon. I'd like to have the separate
> table enhancement, because it is dirt easy to implement.

The ouid scheme will happen soon, but not by April 15th (I'll grant you
that).

> Now, I think that BOTH of these techniques have their place and are
> appropriate for different circumstances.

Agreed.  We don't want a fork if both methods can coexist.  Can you lay out
more coding details for us to help you implement this?

--Todd Owen