> What would be the best way> to communicate with the DB? Would it make sense > just to have one linux> shared library containing the DB API ? (I am a Linux > newbie too -- so this> might be a stupid question -- I am not sure ) Or > perhaps one library for CGI> and one for the application? Or perhaps even a > library for the cgi and the> application have the api as part of it? All this doesn't matter at all. The only restriction - both should use compatible versions of SQLite, i.e. if somewhere there's newer version of SQLite then you don't use its new features. And the easiest way would be to compile SQLite into both your cgi and application.
Pavel On Thu, Sep 22, 2011 at 8:02 AM, david <da...@southtrader.co.za> wrote: > Hi All > > I am developing an embedded system based around Linux. It consists of an > application collecting small amounts of data from the USB port. I wish to > write this to SQLite. This application also needs to read small amounts of > data from the DB. The client interface is via html/cgi on a web server on > the device. The cgi too needs to read and write to the DB. All applications > and cgi are written in C -- so the question is: What would be the best way > to communicate with the DB? Would it make sense just to have one linux > shared library containing the DB API ? (I am a Linux newbie too -- so this > might be a stupid question -- I am not sure ) Or perhaps one library for CGI > and one for the application? Or perhaps even a library for the cgi and the > application have the api as part of it? > > Any suggestions would be most welcome > > Thanks > > David > _______________________________________________ > 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
