I personally like it for embedded (in other applications) jobs because
of its small code footprint compared to a RDBMS.
Tim Anderson wrote:
Many thanks to those who have commented (more are welcome of course;
though I won't be able to use all of them).
I'll post a link to the piece when it
Many thanks to those who have commented (more are welcome of course;
though I won't be able to use all of them).
I'll post a link to the piece when it appears.
Thanks again
Tim
-
To unsubscribe, send email to [EMAIL
A.J.Millan wrote:
John Elrick wrote:
Tim Anderson wrote:
We are working on a project for the Census Bureau and needed an
embeddable database that was zero configuration for the user and fast.
We evaluated SQLite against numerous competitors...
IMHO, a bit exaggerated the "numerous
Tim Anderson wrote:
> I'm writing an article about SQLite and I'd love to get some comments
> from users about why you use it. Performance? Features? Reliability?
> Cost? Is the open source aspect important? Anything else? For that
> matter, anything you really don't like about SQLite?
>
> You can
Am Donnerstag, 7. Juni 2007 19:49 schrieb Tim Anderson:
> I'm writing an article about SQLite and I'd love to get some comments
>
> >from users about why you use it. Performance? Features? Reliability?
>
> Cost? Is the open source aspect important? Anything else? For that
> matter, anything you
John Elrick wrote:
> Tim Anderson wrote:
>
> We are working on a project for the Census Bureau and needed an
> embeddable database that was zero configuration for the user and fast.
> We evaluated SQLite against numerous competitors...
IMHO, a bit exaggerated the "numerous competitors" part of
is in the Washington D.C. metro area. If interested
contact [EMAIL PROTECTED]
-Original Message-
From: Tim Anderson [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 07, 2007 1:50 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] Why do you use SQLite? Comments for an article needed
I'm
John Elrick wrote:
Tim Anderson wrote:
I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about
Tim Anderson wrote:
I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?
You can email me
> I'm writing an article about SQLite and I'd love to get some comments
> from users about why you use it. Performance? Features? Reliability?
> Cost?
- no restrictions, like only 1 LONG VARCHAR in the table, numer of columns,
maximum network packet size and similar (actually there are some
Hi, Tim.
We are using SQLite for two main reasons:
- no daemon needed: to use RDBMS on a cluster machine is quite
annoying. Most clusters administrators does not want more daemons
running.
- SQLite can be very fast when you tweak some of its basic
configuration pragmas, being more than 200%
I am using SQLite because it is easy to use (zero config). To add to your
project. And it was well designed by Mr. Hipp, with a really to use API. A
wild SQL support.
Because there is not Client-Server, and thousands times better than access
and foxpro
Many people uses, so there is a lot of
I'm writing an article about SQLite and I'd love to get some comments
from users about why you use it. Performance? Features? Reliability?
Cost? Is the open source aspect important? Anything else? For that
matter, anything you really don't like about SQLite?
You can email me at
13 matches
Mail list logo
