I would probably take mysql or postgresql, to be able to use the "prepared statements" and other facilities. I don't see any point to implement this kind of system.
or same api as sqlite but the open is taking an url instead, but you have to re-write the api of sqlite. In this case, I can see the benefit of keeping the same code, but as a workaround for some additional non planned requirements, to use a sqlite server instead. (the code stays untouched, just use another dll, same functions same results) anything I missed? Best regards, Sylvain On Mon, May 3, 2010 at 3:27 PM, Gilles Ganault <gilles.gana...@free.fr>wrote: > On Sun, 02 May 2010 21:26:27 +0200, Gilles Ganault > <gilles.gana...@free.fr> wrote: > >It's probably quite an easy thing to do for someone well versed in C, > >but I haven't seen a project that would combine a web server and > >SQLite into a single EXE. > > Here's a diagram: > > http://img222.imageshack.us/img222/6578/wwwsqliteserver.jpg > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
