gives us an advantage by minimizing network
and disk traffic and avoiding repeated process creation and destruction.
In your application my reaction would be to run PostgreSQL or similar
(maybe the new free version of DB/2) on one of your servers and connect
from the others.
Anil Gulati -X (agulati
I have certainly got no desire to change the design goals of SQLite.
The only reason I posted originally is because there was a strong
recommendation in the documentation to use it for web sites which of
course risk concurrent writes... The trouble introduced there in my case
is that I am using
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Appropriate uses for SQLite
"Anil Gulati -X \(agulati - Michael Page at Cisco\)" <[EMAIL PROTECTED]>
wrote:
>
> I am trying to decide whether I can use SQLite for a website that runs
> on 4 load-balanced servers using netwo
database/tables, then PostgreSQL or
MySQL may be the more appropriate choice. They are designed to be
distributed (hence their increased overhead) while SQLite is designed to
be lean-and-mean.
Just my 2 cents worth...
Phil
On Feb 1, 2007, at 7:03 PM, Anil Gulati -X ((agulati - Michael Page at
Cisco
Of Light Software
http://www.polsoftware.com/
-Original Message-
From: Anil Gulati -X (agulati - Michael Page at Cisco)
[mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 8:27 PM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Appropriate uses for SQLite
That's what I'm
unning separate
> > websites from your multiple servers, then why not use 4 instances of
> > SQLite ??
> > That is unless the websites need to share the same database/tables.
> >
> > If they do need to share the same database/tables, then PostgreSQL
> > or
have designed, I have an automatic process that dumps the
db to a text file every 4 hours or so. These are kept for a couple of
days. I sleep easy at night knowing this...
Phil
On Feb 1, 2007, at 7:59 PM, Anil Gulati -X ((agulati - Michael Page at
Cisco)) wrote:
> Thanks for replying P
database/tables, then PostgreSQL or
MySQL may be the more appropriate choice. They are designed to be
distributed (hence their increased overhead) while SQLite is designed to
be lean-and-mean.
Just my 2 cents worth...
Phil
On Feb 1, 2007, at 7:03 PM, Anil Gulati -X ((agulati - Michael Page at
Cisco
Hi SQLite users
Thank you for your attention - I am just hoping for some clarification
of usability of SQLite.
Referring to: http://www.sqlite.org/whentouse.html
- SQLite works well in websites
- Other RDBMS may work better for Client/Server applications
- SQLite will work over a network file
9 matches
Mail list logo
