On 8/6/07, Christian Smith <[EMAIL PROTECTED]> wrote: <snip> > > 2) anybody ever implemented something like a single > > process of sqlite doing queries for a lot of networked > > clients? > > > A few people have implemented such a solution. It loses one of the > benefits of SQLite, however, in that SQLite is no longer admin free.
how so? > > > > > > 3) how big has your sqlite database grown? have you had any trouble > > managing the db? any bad experiences as to stability of > > the db file? > > > Stability of the file? In what sense? Compatibility? Or resistence to > corruption? Or size, perhaps? resistance to corruption in particular. thinking about it, this may be an OS issue but given that the OS is ok, how does sqlite handle it? > > > > > > i am asking all of these is because i'm seriously considering > > sqlite to be used as my sql server for a project. > > > > how i'll implement it looks something like this: > > > > components of app: > > embedded web server > > sqlite > > some scripting language > > > > there will only be one sqlite process which will be forked > > when the web server is launched. queries to sqlite will > > be sent to the sqlite process via sockets. > > > You can do this, but you may find it easier to embed SQLite right into > your app, using whatever wrapper language binding your app is written in. > That is how it's designed to be used. It'll also be faster that way as > well, and easier to manage. thinking about this some. yeah. maybe you're right. <snip> thank you for the response. ./e -- no sig ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
