>>If it has a structure change aren't you going to want to populate the new field(s) on an insert?
>
>Not necessarily. It could be a non-required field whose data is not available at the time of the initial insert and gets populated later via a different process.

Yes, it could be. Personally I would at least initialize it to null rather than rely on chance.