[Phpwebsite-developers] For discussion...

[Brian W. B. <br...@ap...>]

Posted as News to phpwebsite.appstate.edu - not really news, so not posted. 
But thought it might be worth some discussion here...

Kind Regards,
Brian
-- 
Brian W. Brown
Internet Systems Architect, ESS
Student Development
Room 269, John Thomas Hall
Appalachian State University  
Boone, NC 28608

vox: 828-262-7124
fax: 828-262-2585


+---------------------------------------------------+

More elaborate table names in db would be an asset!

While trying to slip into my flame suit, I'd really like to inform the
community here at phpWebSite about the fact, that I kind a like this product
and the communities style considering the openness of the development
process. This product seems to try to meet the needs of its users. Ok,
zipper closed. Ready for  opinions?  

In my experience nearly every software just using sql for a part of its job,
does it in a horrible way. Try to install seven web-products in a hosted
environment with just one db granted access to, and enjoy the chaotic usage
of those seven uniquely named users, comments, article, authors, you-name-it
tables.  Or imagine to wanting use e.g. phpWebSite, ***nuke, etc. in
multiple separate instances each for a different purpose or community, how
to now separate those tables, if having only one db? And if you did, look
forward, next update won't be too smooth. 

Since the language forks might render a patch of 0.75p2 useless for
integrating into the master tree, how might one - possibly me - help? What
do the users think of eg transformations a la:

db table users is renamed phpwebsite_users? 

Also the intro of a phpwebsite_version table might be interesting. Since the
db structure as of 0.75p2 as defined in (german fork's) phpwebsite.sql is
quite simple (no views, rules, triggers and such) the work to be done is in
the embedded (or constructed) sql-statements of the php-code. I did it a few
weeks ago with ***nuke, no problem. By the way there seems to be a high
ratio of common code base between the two products when it comes to the real
work behind the scenes. Any opinions? 

                                    
The wisdom above is automatically combined from components of the foreigners
english framework version 19740701T110000Z. The author considers himself not
responsible, if e.g. the language used does not conform to actual standards.
He does not take any responsibilty for having missed quite some updates. Its
far too late for major patches anyway.