[mailto:[EMAIL PROTECTED]
Sent: 07 September 2007 02:46 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] SQLite or MS Access
On 9/7/07, Andre du Plessis <[EMAIL PROTECTED]> wrote:
[..]
> What I don't understand is how Access, and other DB's are able to
still
> operate much f
On 9/7/07, Andre du Plessis <[EMAIL PROTECTED]> wrote:
[..]
> What I don't understand is how Access, and other DB's are able to still
> operate much faster (maybe not as fast), and still flush file buffers to
> disk, is beyond me. Maybe it really still caches it, I would not be
> surprised if you
sis [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 7 septembre 2007 10:25
> À : sqlite-users@sqlite.org
> Objet : RE: [sqlite] SQLite or MS Access
>
> Well here are my test results (im using Delphi for this one)
>
> This is my insert statement:
>
> INSERT INTO TEST (TEST_ID
The problem was transactions
Thanks all
-Message d'origine-
De : Andre du Plessis [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 7 septembre 2007 10:25
À : sqlite-users@sqlite.org
Objet : RE: [sqlite] SQLite or MS Access
Well here are my test results (im using Delphi for this one
Well here are my test results (im using Delphi for this one)
This is my insert statement:
INSERT INTO TEST (TEST_ID_NO_IDX, NO_INDEX, TEST_DATA, TEST_ID) values
(%d, %s, %s, %d)
This table deliberately has NO index.
1000 inserts took:
Inserting MS Access - 4,043.273 ms
Inserting SQLite
-Ursprüngliche Nachricht-
Von: Michael Martin [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 7. September 2007 10:06
An: sqlite-users@sqlite.org
Betreff: [sqlite] SQLite or MS Access
Hi All,
I've done some benchmarks tests and I wonder where I've made a mistake.
In C# code with SQLite.NET.2.0.1
@sqlite.org
Betreff: [sqlite] SQLite or MS Access
Hi All,
I've done some benchmarks tests and I wonder where I've made a mistake.
In C# code with SQLite.NET.2.0.1 wrapper with sqlite 3.0: 1000 inserts
in a table of two columns -> 168 seconds
In C# code with Jet.Oledb.4.0 with MS Acc
Hi All,
I've done some benchmarks tests and I wonder where I've made a mistake.
In C# code with SQLite.NET.2.0.1 wrapper with sqlite 3.0: 1000 inserts
in a table of two columns -> 168 seconds
In C# code with Jet.Oledb.4.0 with MS Access: 1000 inserts in a table
of two columns ->
BC driver for SQLite,
so
that may satisfy your needs for using the Access front-end, integrating with
other
applications, etc.
Allan Miller
- Original Message -
From: "Allan, Mark" <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Wednesday, September 06, 2
On Wed, 6 Sep 2006 18:05:36 +0100, you wrote:
Hello Mark
I think, either Access or ODBC is not a real good idea.
SQLite is a real good idea, if you need a small embedded database.
So far as I know, its even not a good idea, to compare MySQL and
Postgres to SQLite, because MySQL is a
> -Original Message-
> From: Allan, Mark [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 06, 2006 10:06 AM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] SQLite vs MS Access
>
> Hi,
>
> After successfully using SQLite on an embedded device, we a
On 9/6/06, Allan, Mark <[EMAIL PROTECTED]> wrote:
Hi,
This would be used in place of an MS Access database on a local/network disk. I
believe that SQLite should be quicker for both transactions and queries than
Access. The one draw
I've repeatedly seen database corruption with Access in
Sqlite is far more portable than Access. There is also an ODBC
interface available so that you can use the standard SQL/CLI API.
Just be wary of the fact that Sqlite does not have a server like
PostgreSQL so you may run into some locking situations if you have your
database distributed
t; <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Wednesday, September 06, 2006 1:05 PM
Subject: [sqlite] SQLite vs MS Access
Hi,
After successfully using SQLite on an embedded device, we are now thinking of
using SQLite in a PC application.
This would be used in place of
Mark,
If you looking for accessibility to your SQLITE DB from within other windows
applications (That support ODBC) then there is an ODBC driver for SQLITE
which is probably the most common manner to access databases.
Take a look at the following link.
What level of access is needed from outside of the application? There are
nice GUIs available for SQLite that people could use. There is in theory
ODBC access as well, although my experience with ODBC and SQlite was not
especially happy.
Clay
Allan, Mark said:
> Hi,
>
> After successfully
On 9/6/06, Allan, Mark <[EMAIL PROTECTED]> wrote:
Hi,
After successfully using SQLite on an embedded device, we are now thinking of
using SQLite in a PC application.
This would be used in place of an MS Access database on a local/network disk. I
believe that SQLite should be quicker for both
Hi,
After successfully using SQLite on an embedded device, we are now thinking of
using SQLite in a PC application.
This would be used in place of an MS Access database on a local/network disk. I
believe that SQLite should be quicker for both transactions and queries than
Access. The one draw
18 matches
Mail list logo
