3 ms·

> but if I had used a rdbms from the beginning I might have not "shipped" quite as quickly. I doubt that. As mentioned in the article, migrations with rollback

> but if I had used a rdbms from the beginning I might have not "shipped" quite as quickly. I doubt that. As mentioned in the article, migrations with rollbacks basically solve this problem, and let you iterate through schemas quickly. > Swapping it out for a real rdbms will mean changing a couple of classes anyway, nothing dramatic. In theory, perhaps, but I have yet to see that in practice. I do freelance code review and tutoring for a living, and in every case I've seen, a significant amount of work would be needed to move to a different database.

toyg 11y ago
> As mentioned in the article, migrations with rollbacks basically solve this problem Maybe so, but as I said above, they are another thing to do at a time when things are changing fast and one is more worried about checking whether the application "makes sense" than proving its correctness, so to speak. > I do freelance code review and tutoring for a living, and in every case I've seen, a significant amount of work would be needed Well, duh: if this weren't the case, you wouldn't have been involved in the first place :) What company calls consultants to review code they know how to fix themselves in a few minutes?