I can't see any reason why anyone would spend time on this issue.
1) NULL is not a constraint. All columns are nullable by default
(SQL standard and in all SQL databases to my knowledge).
2) It will not add any new functionality.
3) You will not gain anything in speed, resource usage etc.
Point 5 is the reason, one of the databases I use does not handle no
definition and requires a NULL or NOT NULL definition. But its been a
long time since I checked this so the newer version may be more
compliant. I'll check before I waste any more time on this.
Interestingly derby is the
I just checked - Sybase defaults to NOT NULL but this can be changed as
a database config option.
Thanks
(thinks to self duh)
Bernt M. Johnsen wrote:
I can't see any reason why anyone would spend time on this issue.
1) NULL is not a constraint. All columns are nullable by default
(SQL
Duncan Groenewald wrote:
Any chance someone can explain how I could modify the parser (or
whatever) to be able to handle the NULL constraint ?
Beware: I haven't tried this, but you could have a look at
java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj and
experimentally try to modify
