Show HN: Write universally accessible SQL, not library-specific ORM wrapper APIs

Re:Show HN: Write universally accessible SQL, not library-sp... by zimpenfish on Tuesday August 10, 2021 @12:27PM (#28130821)

> How often does one even migrate DB’s?

I've never seen it happen on a production system in ~20 years.

Might happen at the current gig but that's more down to "Firebase is junk for this job and we're rewriting everything anyway, might as well consider switching DB too".

[ Parent | on HN ]

Re:Show HN: Write universally accessible SQL, not library-sp... by BiteCode_dev on Tuesday August 10, 2021 @01:42PM (#28131842)

Not the point. The point is that people can then build db agnostic libs on top, so that several projects from different teams can use it despite using a different db.

E.G: you can use django, no matter if you are a mysql or a posgreq shop and still use the entire ecosystem of apps.

[ Parent | on HN ]

Re:Show HN: Write universally accessible SQL, not library-sp... by mind-blight on Tuesday August 10, 2021 @01:40PM (#28131819)

I've seen it happen once. Back in 2011, the company I was working for decided to switch all of their apps from MySQL to postgres. We had built everything in Django, so the transition was a lot less painful than it could have been, but it definitely wasn't free.

[ Parent | on HN ]

Re:Show HN: Write universally accessible SQL, not library-sp... by tomrod on Tuesday August 10, 2021 @12:32PM (#28130890)

Lucky! I've done a few.

[ Parent | on HN ]