"DaFrizzler" <DaFrizzler@gmail.com> wrote in message
news:1169564212.277279.81710@k78g2000cwa.googlegro ups.com...
> Hi, I have received the following email from a colleague, and am quite
> frankly baffled by the idea.
>
> I am just wondering if anyone has any advice or suggestions about
> this????
>
>
> === BEGIN MAIL ===
> The DB2 DBA has requested that all columns in the tables be defined as
> not null with default to improve storage, performance, and ease of
> backup/recovery. Currently there are several columns in each table
> that are nullable. By making these columns not null with default,
> there would always be a value in the column, space for char/varchar,
> and 0 for integer/smallint/decimal. Does this cause any problems with
> the Java/Hibernate code? The DBA has indicated that all of the other
> Java applications are defined this way.
> === END MAIL ===
>
>
> Thanks,
> John.

Each nullable column uses one extra byte for the null indicator, so NOT NULL
WITH DEFAULT would save some storage. I don't know about the other claims
regarding performance and ease of backup/recovery.

What kind of advice or suggestions are you looking for?