Why sqlite3 temp files were renamed 'etilqs_*' (2006)
1–10 of 146 posts
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#2Link directly to the reason comment:
https://github.com/mackyle/sqlite/blob/18cf47156abe94255ae14...
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#3[deleted]
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#4Somewhat related - I’m very very curious to hear a detailed account of someone who uses SQLite for a production app with high traffic.
For the embedded use case I think it’s a slam dunk, but there are many interesting use cases for server side but they all seem to be toyish.
The locking behavior of SQLite is somewhat problematic unless you use WAL and even then not perfect
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#5Looks like the line numbers were lost: https://github.com/mackyle/sqlite/blob/18cf47156abe94255ae14...
It's because McAfee started using SQLite, angry users would stumble upon the files, do a minimum of searching or thinking, and be furious at SQLite developers.
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#6Somewhat related - I’m very very curious to hear a detailed account of someone who uses SQLite for a production app with high traffic. For the embedded use case I think it’s a slam dunk, but there are many interesting use cases for server side but they all seem to be toyish. The locking behavior of SQLite is somewhat problematic unless you use WAL and even then not perfect
Fly[1] uses it
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#7Somewhat related - I’m very very curious to hear a detailed account of someone who uses SQLite for a production app with high traffic. For the embedded use case I think it’s a slam dunk, but there are many interesting use cases for server side but they all seem to be toyish. The locking behavior of SQLite is somewhat problematic unless you use WAL and even then not perfect
Wasn't there an article on here within the last week saying how SQLite is "perfect for the 'edge'?"
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#8Love it.
Too bad there aren't enough Mac users to prompt a similar backlash against Macs littering every computer they visit on the network with .DS_Store and other turds.
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#9Somewhat related - I’m very very curious to hear a detailed account of someone who uses SQLite for a production app with high traffic. For the embedded use case I think it’s a slam dunk, but there are many interesting use cases for server side but they all seem to be toyish. The locking behavior of SQLite is somewhat problematic unless you use WAL and even then not perfect
Not a ton of detail, but Tailscale uses it: https://tailscale.com/blog/database-for-2022/
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#10Somewhat related - I’m very very curious to hear a detailed account of someone who uses SQLite for a production app with high traffic. For the embedded use case I think it’s a slam dunk, but there are many interesting use cases for server side but they all seem to be toyish. The locking behavior of SQLite is somewhat problematic unless you use WAL and even then not perfect
Fly[1] uses it 1: https://fly.io/blog/introducing-litefs/
Do they have any customer success stories about sqlite? I've mostly seen (compelling and well written) marketing posts. Details from someone using the product are much more interesting.