On Wednesday 10 Oct 2007, [EMAIL PROTECTED] wrote:
Here is my dilemma: Since only a few rows in the table will be featured
articles I figured it would be bad to have an isfeatured field in the
table.
I'd add the 'isFeatured' column - the opposing point of view is that all the
non-featured
Why have a field for every row when a small minority will actually
use it?
Most database system will use only one byte for a logical value,
sometimes may be only one bit,
so, uless you have zillons of articles, the overhead is marginal.
However, should I really create a table with one field
Thanks for all of the feedback guys.
Terrance had a good suggestion of creating additional starting and ending
date columns for when the articles would be featured, thus justifying the
second table.
Tom, your right that the empty field would signify that the article was not
featured. Is that
Hey all,
Here is my simple use case: I have a table of articles. I would like to
indicates some as featured.
Here is my dilemma: Since only a few rows in the table will be featured
articles I figured it would be bad to have an isfeatured field in the
table. Why have a field for every row when a
and Information Technology
E-mail: [EMAIL PROTECTED]
-Original Message-
From: Aaron Roberson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 9:01 PM
To: CF-Talk
Subject: Help with DB design delimma
Hey all,
Here is my simple use case: I have a table of articles. I would like
make
this process relatively simple.
M!ke
-Original Message-
From: Aaron Roberson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 8:01 PM
To: CF-Talk
Subject: Help with DB design delimma
Hey all,
Here is my simple use case: I have a table of articles. I would like to
indicates
6 matches
Mail list logo
