[TYPO3-core] RFC: Fix FE user login for DBAL
Dmitry Dulepov
typo3 at accio.lv
Wed Jun 28 11:30:09 CEST 2006
Hi!
Franz Holzinger wrote:
> Why? A comparison of a NULL column with '=' or '<>' could also be
> 'false' for some databases. This would be the better result.
I said "true" because I experienced this. Standard says it is
"undefined", so it can be anything! Thus removing NOT NULL without
giving explicit default value is very bad.
> I think, if NULL '=' 3 is true, then this is a bug of the database. And
> NULL '<' 3 should be false and NULL '>' 3 should be false, too.
No, this is SQL standard :) Comparison with NULL produces undefined result.
> However I think it would be managable to correct some lines of code to
> make NULL columns possible.
Why and where do we need null columns?
Dmitry.
--
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
More information about the TYPO3-team-core
mailing list