4 ms·
Huh. I had a client once who complained that I was adding database indirection layers to some application. "When are we ever going to change databases?" I had
by mdpopescu 6y ago
Huh. I had a client once who complained that I was adding database indirection layers to some application. "When are we ever going to change databases?"
I had to remind him that, in the few years I worked for him, we had actually used five different databases - MS SQL, VistaDB, Excel-as-a-database (using ODBC), LiteDB (a NoSql database) and Sqlite. He knew about each and everyone of those, but the "we're never going to change databases" reaction is so ingrained apparently that he just went with it.
And just in case you're going to argue "sure, you used different databases but in different applications" - I just had a programmer change Sqlite to LiteDB, because Sqlite wasn't working properly on his system and it was faster to just change the database.
- ric2b 6y agoI'm very curious about this, what were the reasons for changing between all those databases? You can't be using any advanced features if you're supporting SQL, NoSQL and even Excel, so if you only need basic features why are you bothering with switching so much? I know of one good reason to support multiple databases, when you're writing software for several enterprise clients and each of them wants to use whatever databases their teams are used to managing.