Wait a sec, just because someone misused a term like "DRY" doesn't mean the principle is wrong. Re-representing data models in other execution environments is indeed a repetition - it just normally isn't identified as one, for some reason.

Adding a database field often has repercussions throughout the stack (not to mention throughout the rest of the system).

What's really interesting is to realize that DRY is traditionally only applied to static code, rather than runtime state. But personally I think it should apply to both.