Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SQLite Is a Library of Congress Recommended Storage Format

sqlite.org

Post reply on HN
Print view View original

121–130 of 205 posts

Re: SQLite Is a Library of Congress Recommended Storage Format

#121

Post by haspok »

Fwirt wrote: post #5
alexpotato wrote: post #2

I have always loved SQLite. I have also heard that some firms ban its use. Why? Because it makes it SO easy to set up a database for your app that you end up with a super critical component of your application that looks exactly like a file. A file that can have any extension. And that file can be copied around to other servers. Even if there is PII in that file. Multiply this times the number of applications in your…

The question is, do the same firms ban Excel? Excel spreadsheets often end up as shadow databases in unlikely places.

You can enforce classification and privacy labels (or something similar) in Excel and other document files, at least in a closed corporate environment. Azure also supports this. Also, everyone has Office installed (in a corporate environment), anyone can open and work with an Excel file.

Re: SQLite Is a Library of Congress Recommended Storage Format

#122

Post by b40d-48b2-979e »

Mawr wrote: post #120
llagerlof wrote: post #83

I used SQLite for a few applications several years ago. One time, the database got corrupted and all the data was lost. That was the day I stopped using SQLite. Also, the lack of enforced column data types was always a negative for me.

I used a hard drive for a few applications several years ago. One time, the drive got corrupted and all the data was lost. That was the day I stopped using hard drives.

This isn't the same and you know it.

Re: SQLite Is a Library of Congress Recommended Storage Format

#123

Post by IshKebab »

tmountain wrote: post #116
tnelsond4 wrote: post #33

I'm always inspired by SQLite. Overall I like it, but if you're not doing writes it's really overkill. So I made a format that will never surpass SQLite, except that it's extremely lighter and faster and works on zstd compressed files. It has really small indexes and can contain binaries or text just like SQLite. The wasm part that decompresses and reads and searches the databases is only 38kb (uncompressed (maybe 16…

Overkill in what way exactly? The LOC of the project shouldn't have any bearing on most people's usage of the project. SQLite is one of the well tested and mature projects in the world. What exactly would motivate someone to use PeakSlab instead? What problem are you solving?

Read the comment. He's using it in WASM form and doesn't want users to have to download 1.2MB of SQLite every time they visit the page.

Re: SQLite Is a Library of Congress Recommended Storage Format

#124

Post by b40d-48b2-979e »

Spooky23 wrote: post #13
akihitot wrote: post #8

For public-sector data preservation, it may be one of the best options. The specification is publicly available - It is widely adopted - It is likely to remain readable in the future - It has little dependency on specific operating systems or services - It carries low patent risk From the perspective of long-term continuity, avoiding dependence on any particular company or service is extremely important.

Archivists also love formats close to native. SQLite lets the relational relationships be present in a way that csv cannot.

Foreign keys are not enforced unless you enable it but only for that connection.

Re: SQLite Is a Library of Congress Recommended Storage Format

#125

Post by tnelsond4 »

tmountain wrote: post #116
tnelsond4 wrote: post #33

I'm always inspired by SQLite. Overall I like it, but if you're not doing writes it's really overkill. So I made a format that will never surpass SQLite, except that it's extremely lighter and faster and works on zstd compressed files. It has really small indexes and can contain binaries or text just like SQLite. The wasm part that decompresses and reads and searches the databases is only 38kb (uncompressed (maybe 16…

Overkill in what way exactly? The LOC of the project shouldn't have any bearing on most people's usage of the project. SQLite is one of the well tested and mature projects in the world. What exactly would motivate someone to use PeakSlab instead? What problem are you solving?

I'm solving a simpler problem. Just making cross platform dictionary progressive web apps with indexes and full text search and HTML tags and uppercase letters inserted back into the text on render so they don't interfere with search.

SQLite is 1.2mb in combined wasm and JavaScript and not really designed for my use case, so I would have to add all the things i need anyway like compression and HTML tag insertion. For my use case which is just for pwas SQLite takes too long to load and the files are too big and the search isn't tailored. So I made something else in 38kb instead

Re: SQLite Is a Library of Congress Recommended Storage Format

#127

Post by lenwood »

Just yesterday it occurred to me that it had been a while since I last saw an SQLite post at the top of HN.

I really like the simplicity and speed of SQLite, I've used in both personal and professional projects. For day-to-day work I still end up in Excel, not because I like it more (I don't), but because its ubiquity makes it the lowest friction way to share & explore datasets with less technical stakeholders and execs.

Re: SQLite Is a Library of Congress Recommended Storage Format

#128

Post by raxxorraxor »

chungy wrote: post #118
raxxorraxor wrote: post #100

Earlier quoted context omitted.

SQLite is simple in its own way and I like the design principle of their SQL dialect. "Right joins are just left joins in the wrong direction, you don't need that crap" Of course it always gets simpler or more specialised. I think many apps using databases would run with SQLite just as well. And some would probably run just as well with a textfile instead of any db like SQLite.

> "Right joins are just left joins in the wrong direction, you don't need that crap" SQLite has supported all types of joins since version 3.39 in 2022.

Well, look at that, now it is downhill from here!

Re: SQLite Is a Library of Congress Recommended Storage Format

#129

Post by jnwatson »

haspok wrote: post #121
Fwirt wrote: post #5

Earlier quoted context omitted.

The question is, do the same firms ban Excel? Excel spreadsheets often end up as shadow databases in unlikely places.

You can enforce classification and privacy labels (or something similar) in Excel and other document files, at least in a closed corporate environment. Azure also supports this. Also, everyone has Office installed (in a corporate environment), anyone can open and work with an Excel file.

I don't have Office installed, nor do a significant majority of my peers. Given that sqlite is installed by default on Macs, a sqlite file is far more portable than an Excel file.

Re: SQLite Is a Library of Congress Recommended Storage Format

#130

Post by IshKebab »

tombert wrote: post #42
topham wrote: post #27

Earlier quoted context omitted.

The problem with it is you didn't solve your biggest actual problem, you just haven't had a problem bite you in the ass yet so you think your problem is solved.

I am not sure the problem is actually fully solvable. I think SQLite helps at least a little.

It's totally solvable and SQLite solves it (or claims to anyway). The real question is if it works. To test this sort of thing properly you really need what is now called DST and I'm not sure SQLite does that. It is pretty well tested though so they've probably done at least some testing of it.
Post reply on HN