Re^6: DBI: passing undef as an argument

How is that better than if we put NULL into field and will check if it is not NULL? Actually if we allow NULL values for the column it is implemented as additional boolean flag for the column, so what you're proposing is just reimplementing of existing mechanism.

Comment on Re^6: DBI: passing undef as an argument

Replies are listed 'Best First'.
Re^7: DBI: passing undef as an argument by CountZero (Bishop) on Aug 09, 2009 at 21:11 UTC
Because --as you can read in my other post in this thread-- "NULL" breaks the relational model and the meaning of "NULL" is ambiguous and such meaning cannot be derived from the database itself but must come from external sources. Meditate upon it and you will see I'm right ;-) CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]

Replies are listed 'Best First'.

Re^7: DBI: passing undef as an argument
by CountZero (Bishop) on Aug 09, 2009 at 21:11 UTC

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

[reply]