actualy i'm not soo smart..
> Max Thayer wrote:
> > I'm using MySQL 5.x InnoDB engine, transactional tables. I have a
> > conceptual design question. If I have a two columns 'a' and 'b', a is
> > the primary key, and b is a type double, in table 1 (T1) for which
> > column b will have many NULL v
Max Thayer wrote:
I'm using MySQL 5.x InnoDB engine, transactional tables. I have a
conceptual design question. If I have a two columns 'a' and 'b', a is
the primary key, and b is a type double, in table 1 (T1) for which
column b will have many NULL values, do I leave it with an allow null
cons
the business logic says it's
needed, at application run time if certain conditions were met, the
column takes on the characteristic NOT NULL attribute.
-Original Message-
From: Dan Shirah [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 3:50 PM
To: Max Thayer
Cc: php-db@list
al Message-
From: Dan Shirah [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 3:50 PM
To: Max Thayer
Cc: php-db@lists.php.net
Subject: Re: [PHP-DB] DB Design Concepts
Max,
I am assuming that since column b will only be populated 7% of the time
that it is not a value specific column (does not
Max,
I am assuming that since column b will only be populated 7% of the time that
it is not a value specific column (does not matter if it has a value or not)
Therefore I would suggest leaving the NULL's in there as it will not (at
least should not) affect any system performance.
On 5/2/07, Ma
