Re: [sqlite] sqlite as server queries
Edwin Eyan Moragas uttered: On 8/6/07, Christian Smith <[EMAIL PROTECTED]> wrote: 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? Because now you need to manage port numbers, multiple processes on potentially multiple machines. Not massive overhead, but still not as easy as starting or stopping your one process. 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? SQLite uses a rollback journal along with timely OS level syncs to ensure the database is always in a consistant or recoverable state. SQLite can survive OS or hardware failure so long as the filesystem remains intact. thank you for the response. ./e Christian -- /"\ \ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL X - AGAINST MS ATTACHMENTS / \ - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] sqlite as server queries
On 8/7/07, Gilles Ganault <[EMAIL PROTECTED]> wrote: > At 14:08 06/08/2007 +0100, "Edwin Eyan Moragas" wrote: > >2) anybody ever implemented something like a single process of sqlite > >doing queries for a lot of networked clients? > > Am working on this, in Classic VB5: Winsock control on the server, Inet > control on the client, the client thinks it's talking to a web server. > > http://codecomplete.free.fr/sqlite/sample/ > G, thanks a lot ./e -- no sig - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] sqlite as server queries
At 14:08 06/08/2007 +0100, "Edwin Eyan Moragas" wrote: 2) anybody ever implemented something like a single process of sqlite doing queries for a lot of networked clients? Am working on this, in Classic VB5: Winsock control on the server, Inet control on the client, the client thinks it's talking to a web server. http://codecomplete.free.fr/sqlite/sample/ G. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] sqlite as server queries
On 8/6/07, John Stanton <[EMAIL PROTECTED]> wrote: > > > We use a single process server as an Sqlite server. It works well > because it obeys certain constraints: >o Transactions are always short >o It has many users and many Sqlite databases, but each database > does not have a large number of users, or more correctly a large traffic > rate. >o Row scans are avoided on large tables. > > The benefits are the ease of maintenance of multiple databases, each one > being just a file. Transactions complete typically in less than 500uS. sounds good. > > We use HTTP protocol to access the Sqlite server, and it allocates one > or two threads to each user connection (a browser will try to open two > connections). > > If you have large transactions or large numbers of users sharing a > database, consider using something like PostgreSQL, Oracle or DB/2. > Sqlite is inherently single streamed and that imposes a cap on its > ability to handle many simultaneous connections to a single database. this is a personal project and i really want to use sqlite. thanks for this. i'm a big pg fan. thank you. ./e -- no sig - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] sqlite as server queries
On 8/6/07, Christian Smith <[EMAIL PROTECTED]> wrote: > > 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. thank you for the response. ./e -- no sig - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] sqlite as server queries
Edwin Eyan Moragas wrote: hi group, i have several small questions for the group any experiences or thoughts shared would be greatly appreciated. 1) anybody used sqlite as a sql server? i'm thinking of say using the embedded sqlite in PHP5 or similar. 2) anybody ever implemented something like a single process of sqlite doing queries for a lot of networked clients? 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? 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. i can see that the queries will be sequential. no problems there. i'm not worried with speed at the moment. i just want to know if this has been done before and i'd like to solicit wisdom from the group. thank you. ./e We use a single process server as an Sqlite server. It works well because it obeys certain constraints: o Transactions are always short o It has many users and many Sqlite databases, but each database does not have a large number of users, or more correctly a large traffic rate. o Row scans are avoided on large tables. The benefits are the ease of maintenance of multiple databases, each one being just a file. Transactions complete typically in less than 500uS. We use HTTP protocol to access the Sqlite server, and it allocates one or two threads to each user connection (a browser will try to open two connections). If you have large transactions or large numbers of users sharing a database, consider using something like PostgreSQL, Oracle or DB/2. Sqlite is inherently single streamed and that imposes a cap on its ability to handle many simultaneous connections to a single database. For a scripting language we implemented Javascript to be sympathetic to application programmers already using JS in their web pages. Sqlite can execute Javascript functions and Javascript programs can call Sqlite. We insulate the server from SQL injection attacks by storing a library of SQL on the server in the form of RPCs and never sending it from the client. Finally, using a server to share Sqlite on a network is more robust than using file sharing. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] sqlite as server queries
Edwin Eyan Moragas uttered: hi group, i have several small questions for the group any experiences or thoughts shared would be greatly appreciated. 1) anybody used sqlite as a sql server? i'm thinking of say using the embedded sqlite in PHP5 or similar. 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. 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? 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. i can see that the queries will be sequential. no problems there. i'm not worried with speed at the moment. i just want to know if this has been done before and i'd like to solicit wisdom from the group. I have thoughts on wrapping SQLite with FreeTDS, in order to provide networked access to legacy apps that expect a TDS server to talk to. But that is more for legacy reasons. You don't have this legacy burden by the sounds of it, so just embed SQLite. thank you. ./e Christian -- /"\ \ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL X - AGAINST MS ATTACHMENTS / \ - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] sqlite as server queries
hi group, i have several small questions for the group any experiences or thoughts shared would be greatly appreciated. 1) anybody used sqlite as a sql server? i'm thinking of say using the embedded sqlite in PHP5 or similar. 2) anybody ever implemented something like a single process of sqlite doing queries for a lot of networked clients? 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? 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. i can see that the queries will be sequential. no problems there. i'm not worried with speed at the moment. i just want to know if this has been done before and i'd like to solicit wisdom from the group. thank you. ./e -- no sig - To unsubscribe, send email to [EMAIL PROTECTED] -
