[TYPO3-dev] TYPO3 and Oracle

[Martin Kutschker]

Dmitry Dulepov schrieb:
> Hi!
> 
> Martin Kutschker wrote:
> 
>> It seems that the new version of TYPO3/DBAL will drop the NOT NULL 
>> defintion from the fields. So you'll won't need them with the next 
>> release.
> 
> 
> 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.

Masi