> 2) Same as above, but the engine writes to both new and deprecated
> columns. 100% compatibility, but code duplication.

I guess this is the way to go. Can't we use triggers to populate
deprecated columns, so the only duplication happens during the storage?

Roman