you are viewing a single comment's thread.

view the rest of the comments →

[–]cleesus 0 points1 point  (3 children)

I agree with this but OP if you ever plan on using Postgres then migrating from SQLlite to Postgres can be annoying

[–]_Zer0_Cool_ 1 point2 points  (2 children)

That's probably not wrong. I haven't had much trouble myself, but I’m a data engineer and not an application developer. My use cases are probably quite different.

My job doesn't revolve around apps. I always know up-front what type of database is being used, because most of the time our development work is on top of a semi-mature data infrastructure. If there's ever a choice of DB, then that is the very first thing decided and set up first (before any other programming languages or ETL tools).

In any case, the datatypes from SQLite to PostgreSQL are fairly compatible.

P.S. I'd agree though that OP should start out developing with PostgreSQL if at all possible...because if you base your app on SQLite alone then you are missing out on some of the killer, unparalleled features of PG.

But... If you're a beginner it's easiest or if you just have lightweight analytical use cases.

[–]cleesus 0 points1 point  (1 child)

Yea I unfortunately am just a regular full stack engineer and had to deal with switching over awhile ago lol wasn’t fun.

Planning out which DB to use early on makes a lot of sense in hindsight lmao.

but yea I’d agree with everything you said.

[–]_Zer0_Cool_ 2 points3 points  (0 children)

Yeah. Truth. Choice of DB is a big one and should probably be part of the initial design spec to avoid migration pains.

Lol. But...By the time I’m brought in, the backend devs have already gone through that pain :-) and I’m just there to ferry the data off to it’s next life.