News for hackers. Stuff that matters.
Re:The Design Of SQLite4 by jqm on Sunday May 25, 2014 @04:27PM (#7797458)
I love sqlite and find it extremely useful. I just wish they could figure the multi-user issues out (maybe it's not practical...probably not, I don't know how it works internally). But, if they could do this it would be truly awesome!
Re:The Design Of SQLite4 by ghshephard on Monday May 26, 2014 @05:05AM (#7799144)
From: http://www.sqlite.org/whentouse.html

SQLite is not designed to replace Oracle. It is designed to replace fopen().

Re:The Design Of SQLite4 by panzi on Sunday May 25, 2014 @08:00PM (#7798092)
Easy: Put a server process in front of it and route access to the DB through that. :P
Re:The Design Of SQLite4 by eyko on Sunday May 25, 2014 @09:41PM (#7798323)
Doesn't that just defeat the purpose? At that point you're probably much better off just using postgressql (or similar).
Re:The Design Of SQLite4 by nikbackm on Monday May 26, 2014 @03:27AM (#7799010)
It might be a neat solution if you already have a server process for other tasks anyway and the data access needs are quite simple.
Re:The Design Of SQLite4 by jqm on Sunday May 25, 2014 @09:59PM (#7798362)
That's what I'm thinking. Probably less trouble just to set up postgres at that point and not deal with unexpected troubles and complications.

But I hadn't thought of putting a server process in front of sqlite so thanks for the tip. It might come in handy at some point.

Re:The Design Of SQLite4 by jqm on Monday May 26, 2014 @08:56AM (#7799550)
would someone care to explain why they down voted that comment?
Re:The Design Of SQLite4 by panzi on Monday May 26, 2014 @02:15PM (#7800842)
It was a joke! Hence the ":P".
Re:The Design Of SQLite4 by genwin on Sunday May 25, 2014 @09:50PM (#7798340)
I did that, using Go and its channels feature. Not much code and works like a charm.