{"author_name":"JunichiIto","categories":["\u30b7\u30b9\u30c6\u30e0\u958b\u767a"],"title":"When Database Source Control Goes Bad \u7ffb\u8a33 Part4","type":"rich","height":"190","blog_url":"https://blog.jnito.com/","url":"https://blog.jnito.com/entry/20101027/1288129172","published":"2010-10-27 06:39:32","description":"\u300cThe Catch\u300d\u306e\u5f8c\u534a\u90e8\u5206\u3067\u3059\u3002\u8a18\u4e8b\u5168\u4f53\u304b\u3089\u3059\u308b\u3068\u305d\u308d\u305d\u308d\u6298\u308a\u8fd4\u3057\u5730\u70b9\uff1f\u3044\u3084\u3042\u9577\u3044\u3067\u3059\u306d\u301c\u3002 Anyhow, during the next deployment to QA, someone needs to remember that these specific changes need to get deployed. Since there is no defined strategy for tying database changes to code changes, every time code is deployed there is a little bit of \u2026","image_url":null,"author_url":"https://blog.hatena.ne.jp/JunichiIto/","blog_title":"give IT a try","width":"100%","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fblog.jnito.com%2Fentry%2F20101027%2F1288129172\" title=\"When Database Source Control Goes Bad \u7ffb\u8a33 Part4 - give IT a try\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","version":"1.0","provider_url":"https://hatena.blog","provider_name":"Hatena Blog"}