3 ms·
That sounds all kinds of wrong. > The argument that SQLite files can theoretically be 281 Terabytes large is a spurious one. And it is being purported by the S
by Tomte 4y ago
That sounds all kinds of wrong.
> The argument that SQLite files can theoretically be 281 Terabytes large is a spurious one. And it is being purported by the SQLite team despite them knowing better.
and
> Think about it: Do you know how large the biggest hard disks or SSDs are nowadays? They’re not much larger than maybe 10 Terabyte.
Wow. Your file-based database is limited by your available space. Shocker!
What insane amounts of data are we talking about?
> [Name] asked what the best way would be to store about 16GB of research data efficiently
So it's 16 GB. My SSD can handle that.
> The biggest limit is physics
Ah, physics! Good old Bekenstein bound. No?
Let's move on.
> When I created the database in the first place, it created a pretty basic index
and
> But as soon as I tried to search for something that was not indexed – the filename column –, SQLite had to actually open the database file and check every single entry from the very beginning until it found the entry I was looking for.
So you're doing it wrong, you even know you're doing it wrong, you know what to do, but you definitely don't want maybe issue a CREATE INDEX?