3 ms·
Out of curiosity, how many times in your career have you decided to switch databases halfway into a project? In 15 years of doing this for a living, I've never
by jasonkester 18y ago
Out of curiosity, how many times in your career have you decided to switch databases halfway into a project?
In 15 years of doing this for a living, I've never actually needed to do so. With that in mind, I don't feel particularly worried that my SQL is not instantly portable.
- deleted 18y ago[deleted]
- silentbicycle 18y agoI've moved from sqlite to serialization via Lua on one, when clarifying the problem made it clear that using a relational database was actually a poor fit. Most of my examples aren't database-related, though. I agree that switching databases doesn't happen much, I'm just noting that having a major, conceptually distinct part of a project entangled with the others is usually a sign of other problems. (Maybe that's just my experience maintaining legacy codebases, though.) I think that getting preoccupied with moving from one database to another for scalability reasons is usually wishful thinking -- it's like worrying about all the positive attention you're getting.