5 ms·
I already said this in another thread, it's not about switching databases in one project, but using the same skillset across projects regardless of the database
by towelguy 12y ago
I already said this in another thread, it's not about switching databases in one project, but using the same skillset across projects regardless of the database.
- brlewis 12y agoCan you use the same skillset across projects regardless of the ORM, or do you have to standardize on one? Why not just standardize on one database?
- spacemanmatt 12y agoI find SQL is pretty portable. You have to learn each server's ins and outs to do performance work, but then, those differences are part and parcel of why there are different servers, beyond basic business-competitive reasons. ORMs just add a thick layer of fluff over an otherwise (mostly) portable language, where I'm concerned. I rather keep it simple between DBs and apps. If there is gross SQL in the app, make a view or function in the database. It isn't rocket surgery but you do need experienced staff to get it right.