[TYPO3-dev] TYPO3 and Oracle

[Franz Holzinger]

Martin Kutschker a écrit :
>>
>> Not good because result of comparison is undefined when column is null
>> according to SQL standard. So, if it is null, both of these will be
>> true at the same time:
>>
>> x = 'a'
>> x <> 'a'
>>
>> Bad change in my opinion.
> 
> 
> What if we drop the NOT NULL but enforce a DEFAULT even if none is
> specified? So we don't have the ''/NULL ambiguity in Oracle but
> effecitvely have no NULL values in the DB.
> 
I think this is a good solution to remove the 'NOT NULL' for all tables.
defaults:
0 for numbers
'' for texts

It might become too complex to have different solutions for different
databases.