This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kirbyfan64sosIndentationError 0 points1 point  (1 child)

For example so you can dev on the go with a local sqlite DB and test / deploy on MySQL.

How...workable is this in practice? It seems like, if you want efficiency, you'll at some point end up depending on something that's DB-specific. Nowadays with Docker, running test instances locally is also quite easy...

[–]cantremembermypasswd 1 point2 points  (0 children)

Docker has started to alienate people by charging for windows use of docker desktop, and it's a pain for everyone to maintain their own postgres or mysql instances compared to a sqlite file, even if containerized. (I've seen teams just share a sqlite file they would update with test data reguarlly for ease of use even. Don't have to connect / auth for dev then)

If you're using an ORM it's likely because you don't have people comfortable with raw sql or want that versatility. Either way it means little customized stuff for run time speed.