Perl-Sensitive Sunglasses | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Indeed, the DRY principle was the underlying motivator for my asking this question -- why do I have this in two places, and how am I going make sure they stay synchronized?
I do have scripts that (re-)construct and (re-)populate the database. I'm really glad you brought that up, because considering them as part of the constellation of things that needs to stay in sync is leading me toward an approach I think I'm comfortable with. I'm now inclined to the constants in the code and generating the database table based on those same constants that the production code relies on. Of course I'll back that up with tests to make sure that I don't do something dumb like change the constants without reflecting those changes in the database. Thinking about it that way removes a lot of the unease I was feeling about this data being spread around instead of having one source of Ultimate Truth. Thanks for the replies, everyone! $perlmonks{seattlejohn} = 'John Clyman'; In reply to Re: Re: Synchronizing constants/enums in database and code
by seattlejohn
|
|