[TYPO3-dev] TYPO3 and Oracle

[Dmitry Dulepov]

Hi!

Martin Kutschker wrote:
> 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.

This is the best solution. Looks like it covers all cases. According to 
standard, DB must insert explicit default value if none is specified in 
INSERT/UPDATE query. Since we do not insert NULLs explicitely, we are safe.

Dmitry.
-- 
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)