Re: SQL defaults (was Programming a trigger audit in ILE)

[Paul Tuohy <tuohyp@xxxxxxxxxxxxx>]

OK, so I'm not Kent or Bruce - but you are correct. The default in SQL 
is that columns are null capable unless you say otherwise.

Interactive SQl does put in "not null with default" but..... if you look 
at the Create Table function in the database portion of Ops. Nav. the 
default is Null Capable. This is the same as any other version of SQL I 
have worked with (which isn'y saying a lot <g>).

IIRC - If I Recall (or Remember) Correctly.

Paul

Jon Paris wrote:
>  >> Perhaps nitpicking, but (IIRC) with SQL you have to define "ALLOW NULL"
> for fields to accept null value, just as with DDS.
>
> Not sure what IIRC means and I have no problem with nitpicking (I'm told I
> can be really good at it <grin> but ... I have to disagree with you.
>
> By default, fields in SQL are null capable.  In other words ALLOW NULL is
> the default - BUT the _interactive_ SQL tool does automatically put in "Not
> null with default" for you if you create files using prompted SQL.  So,
> SQL's default is null capable but the tool adds the override information
> (assumedly for compatibility with DDS).
>
> Least that's the way I understand it - where's Kent Milligan or Bruce
> Hoffman when you need them?
>
> Jon Paris
> Partner400