[TYPO3-core] RFC: Fix FE user login for DBAL

[Franz Holzinger]

Hello Dmitry,

>Martin Kutschker wrote:
>  
>
>>But the real issue is that I cannot insert/update '' on a NOT NULL 
>>column in Oracle. *sigh* So NOT NULL and DEFAULT '' don't work together.
>>    
>>
>
>But '' is very good default value. We cannot remove NOT NULL just 
>because Oracle treats empty string is null. If we do it, we will allow 
>NULL values in many columns and many queries will break. Result of 
>comparison is undefined if column has null as value. Thus = and <> will 
>be both true for this column. This is even worse!
>  
>
Why? A comparison of a NULL column with '=' or '<>' could also be
'false' for some databases. This would be the better result.

>Thus = and <> will be both true for this column.
>
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.

However I think it would be managable to correct some lines of code to
make NULL columns possible.
Why not change the program code for these cases?

Greets,

Franz