Claudio Nanni wrote:
> Hi everybody I want to join as well.
>
>
> The question is: "Will I allow a record to contain a 'non-informative'
> field
> ?"
No! thats not the question!
> [a] Ok, go ahead.
> [b] No, set the field as NOT NULL
>
> If you choose [b] please assume your responsibilities.
> Everytime you insert a record, either you have all the information at once
> or use your fake,
> fantasy value {0,-99999.9999,-1,PIPPO}.
> If I read your record about the weather in Amsterdam and I read a
> temperature of -99999.9999
> I will definitely think your database is unreliable.
>
No I would not allow this -9999 value to be viewed by the end user. And
you guys take a hypothetical example and think I want to use that
everywhere.
My point is about using null or not.
In a single data, obviously there will some data required, and some data
optional, and I am not talking about the required data, I am talking about
the optional data, and that null is the worst choice for an initial value.
This is from an application design perspective, not while you a creating a
table or constructing an insert statement.
So instead of thinking that I am an idiot, try using your intelligence and
try to understand what I am really talking about!
Mike.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
