>>And considering the possibility of converting/rewrite of code to a different language or platform, it's probably good to avoid relying on implementation-specific behavior in your code.
Fair enough- though I'd take a step back and ask why it's necessary in the first place to insert into tables that may or may not have some of the insert fields. Many other development environments will assume you've subclassed for distinct use cases since the distinction presumably extends beyond the insert.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
