21–30 of 68 posts
Earlier quoted context omitted.
Setting up Postgres is a PITA compared to SQLite. It comes bundled with python these days. Obviously it's going to be a trade off as to which one causes you more pain.
agreed, running pg locally is a pain. I use a cloud postgres instance (even for local dev). They're dirt cheap and it's not worth the hassle of working with a local pg.
My prediction: SQLite will keep gaining popularity. Especially among pragmatic software builders who run their own business and do not work for the man. A demographic that I expect to grow. Talking about SQLite: Is there any downside to partitioning an SQLite db into multiple files? For example one of my systems has a table 'details' which is not vital for the system to work. It's just a nice to have, to have data in…
>Especially among pragmatic software builders who run their own business and do not work for the man.
That's the perfect use case for a SaaS database. Administering a database adds zero business value and you'd be doing it to save at most $50 a month.
> It already seems to be an afterthought after Gigapipe and Firebolt debuts. This is referring to Clickhouse Inc. and is way off the mark. If you're looking for hosted Clickhouse, why would a company whose CTO is the creator of Clickhouse be an "afterthought"? Their cloud product offers separation of storage and compute, but you still have an escape hatch to self-hosting if you need it (which you wouldn't have with F…
And why would one use Clickhouse vs Sql Server as the backing store for OLAP? Is it that much cheaper?
Earlier quoted context omitted.
agreed, running pg locally is a pain. I use a cloud postgres instance (even for local dev). They're dirt cheap and it's not worth the hassle of working with a local pg.
which cloud do you use for local dev?
My prediction: SQLite will keep gaining popularity. Especially among pragmatic software builders who run their own business and do not work for the man. A demographic that I expect to grow. Talking about SQLite: Is there any downside to partitioning an SQLite db into multiple files? For example one of my systems has a table 'details' which is not vital for the system to work. It's just a nice to have, to have data in…
> Especially among pragmatic software builders who run their own business and do not work for the man. A demographic that I expect to grow. From the FAQ; the are lots of caveats (especially, the last). > Situations Where A Client/Server RDBMS May Work Better > Client/Server Applications > If there are many client programs sending SQL to the same database over a network, then use a client/server database engine instea…
I believe this is a reference to enterprises that have different users querying the database directly with SQL that they wrote over a network to a central database.
What about graph databases? Where do they fit? Is there a report or comparison for them?
Earlier quoted context omitted.
> Especially among pragmatic software builders who run their own business and do not work for the man. A demographic that I expect to grow. From the FAQ; the are lots of caveats (especially, the last). > Situations Where A Client/Server RDBMS May Work Better > Client/Server Applications > If there are many client programs sending SQL to the same database over a network, then use a client/server database engine instea…
For me an important caveat is the typing. With all respect for the original author of SQLite -- he has done an outstanding job-- I think he underestimates the value of a good typing system. I have seen some databases that had all kinds of messy data. Back in the day MySQL was also quite loose with regards to checking data. Undoing the damage is in most cases not possible. For a business data is more important than co…
I don't think so. For example, pgsql had an array type before it got JSON, so the drivers can't automatically convert arrays that you want to insert into JSON. With my SQLite ORM, you can just insert arrays and objects and it knows to convert them automatically to JSON.
I like that SQLite just has a few primitive types. My ORM will be able to build on top of them. For example, JavaScript will soon be adding new date types (Temporal), and I will create new types for that, which will be stored as text ultimately.
My prediction: SQLite will keep gaining popularity. Especially among pragmatic software builders who run their own business and do not work for the man. A demographic that I expect to grow. Talking about SQLite: Is there any downside to partitioning an SQLite db into multiple files? For example one of my systems has a table 'details' which is not vital for the system to work. It's just a nice to have, to have data in…
The very problem of SQLite: Single user only. Although SQLite does have WAL but it still doesn't allow you to do concurrent write unless you want to see file corruption. This means SQLite is very much locked to things that works with one specific purpose and almost nothing else. Sure, you can be read-only, but you have to run alongside the app in the specific node, too. Another problem (although without solving the s…
Ps. I would like to test firebolt, sounds promising.