On Tue, Nov 19, 2002 at 11:26:09AM +0100, Jens Frank wrote:
current_articles
current_binaries
current_discussions
previous_articles
previous_binaries
previous_discussions
Knowing whether something is an article, binary, or a discussion seems
to cover what we need.
You would have to double a lot of effort: You need separate SQL-statements
for things like update_article, update_discussion, update_wikipedia, ....
Using a namespace you just have one additional attribute to keep track of
and your code stays simple and readable.
Au contraire. I believe the code would become more simple and readable.
Notice I never suggested "a table per namespace". I suggested only the
6 tables that covered every circumstance I could think of.
And there are already a lot of queries; having less queries and making
of them refer to a slightly different set of tables doesn't strike me as
in any way complicating things. The complication comes when you
shoehorn different things into the same table.
My question remains, do we need namespaces for any other reason than to
know whether the row represents an article, binary, or discussion?
Jonathan
--
Geek House Productions, Ltd.
Providing Unix & Internet Contracting and Consulting,
QA Testing, Technical Documentation, Systems Design & Implementation,
General Programming, E-commerce, Web & Mail Services since 1998
Phone: 604-435-1205
Email: djw(a)reactor-core.org
Webpage:
http://reactor-core.org
Address: 2459 E 41st Ave, Vancouver, BC V5R2W2