News for hackers. Stuff that matters.
Re:It’s About Time for Time Series Databases by wenc on Thursday January 25, 2018 @01:11PM (#16233023)
I looked into SQLite a while ago, and it wasn't so much its robustness that was the deal-breaker, but more the fact that it couldn't handle writes from parallel processes from multiple users (i.e. concurrency) like a normal SQL database could.

I see SQLite as a file-format with a SQL interface.

Re:It’s About Time for Time Series Databases by amyjess on Thursday January 25, 2018 @05:13PM (#16235204)
> I see SQLite as a file-format with a SQL interface.

I love the description from SQLite's website on the subject:

> SQLite does not compete with client/server databases. SQLite competes with fopen().

https://www.sqlite.org/whentouse.html

Re:It’s About Time for Time Series Databases by da_chicken on Thursday January 25, 2018 @02:52PM (#16233990)
Yep. Parallel performance is the biggest issue I've seen with SQLite.

SpiceWorks is the biggest example of a product that doesn't scale because they've elected to use SQLite (and only SQLite). There's no hard limit on the number of devices, but most people say not to exceed about 1,000 devices. We tested it out against 800 devices. We started it on Friday. On Monday, it was still running.

The only other issue I've seen with it is with the data typing. Type inference is much weaker than strict typing, and sometimes it doesn't quite store things the way you'd expect. Granted, the last time I saw problems with that was years ago, but I've seen it.

Re:It’s About Time for Time Series Databases by baldfat on Thursday January 25, 2018 @03:54PM (#16234569)
There are plenty of problems that don't need parallel performance.
Re:It’s About Time for Time Series Databases by da_chicken on Thursday January 25, 2018 @04:45PM (#16234990)
And there are plenty that do. What's your point?
Re:It’s About Time for Time Series Databases by mixmastamyk on Thursday January 25, 2018 @05:08PM (#16235162)
Because some won’t consider sqlite even for those that don’t.
Re:It’s About Time for Time Series Databases by dfox on Thursday January 25, 2018 @02:12PM (#16233602)
There is Berkeley DB/SQL (now sadly owned by Oracle), which is essentially Sqlite with BDB instead it's original B-tree implementation, that supports multiple parallel writers. Also Firebird can be used as in-process embedded database and supports multiple writers (in fact in the server mode it uses same file-locking based synchronisation mechanisms as in embedded mode)

On the other hand it is somewhat rare to see aplication that really needs multiple writers and would not be better served by full fledged database server.

Re:It’s About Time for Time Series Databases by fpoling on Friday January 26, 2018 @07:25AM (#16238608)
Berkley DB is not as reliable as SQLite. Subversion, before switching to own storage, where known for data corruption problems attributed to Berkley DB.
Re:It’s About Time for Time Series Databases by amyjess on Friday January 26, 2018 @10:33AM (#16239888)
I remember the old days when people would refer to berkdb as "Berserkley" because it tended to go berserk on your data. It's always had a bad reputation for reliability.
Re:It’s About Time for Time Series Databases by xapata on Friday January 26, 2018 @10:26PM (#16244675)
It can handle some degree of concurrency via threading.