On 27Aug2012 13:41, bruceg113...@gmail.com bruceg113...@gmail.com wrote:
| When using the database on my C Drive, Sqlite performance is great! (1S)
| When using the database on a network, Sqlite performance is terrible! (17S)
Let me first echo everyone saying not to use SQLite on a network
On Tuesday, August 28, 2012 4:27:48 AM UTC-4, Cameron Simpson wrote:
On 27Aug2012 13:41, bruceg113...@gmail.com bruceg113...@gmail.com wrote:
| When using the database on my C Drive, Sqlite performance is great! (1S)
| When using the database on a network, Sqlite performance is terrible!
Try incrementing the variable cursor.arraysize a lot.
Pedro.
On Tue, Aug 28, 2012 at 11:20 PM, Dennis Lee Bieber
wlfr...@ix.netcom.com wrote:
On Tue, 28 Aug 2012 10:25:35 -0700 (PDT), bruceg113...@gmail.com
declaimed the following in gmane.comp.python.general:
Doesn't the last paragraph
Am 27.08.2012 03:23, schrieb bruceg113...@gmail.com:
My program uses Python 2.6 and Sqlite3 and connects to a network
database 100 miles away.
Wait, isn't SQLite completely file-based? In that case, SQLite accesses
a file, which in turn is stored on a remote filesystem. This means that
there
On Monday, August 27, 2012 8:50:15 AM UTC-7, Ulrich Eckhardt wrote:
Am 27.08.2012 03:23, schrieb bruceg113...@gmail.com:
My program uses Python 2.6 and Sqlite3 and connects to a network
database 100 miles away.
Wait, isn't SQLite completely file-based? In that case, SQLite accesses
Uli,
Answers to your questions:
1) There are approx 65 records and each record is 68 bytes in length.
2) Not applicable because number of records is fixed.
3) Takes less than a second to read all 65 records when all is well.
Takes 17 seconds to read all 65 records when all is NOT WELL
4)
Is there a reason that you're using SQLite in a network environment rather than
a database server?
--
http://mail.python.org/mailman/listinfo/python-list
Demian,
I am not a database expert!
I selected sqlite for the following reasons:
1) Ships with Python.
2) Familiar with Python.
3) The Sqlite description at http://www.sqlite.org/whentouse.html appears to
meet my requirements:
Very low volume and concurrency, small datasets, simple to use.
bruceg113 wrote:
I selected sqlite for the following reasons:
1) Ships with Python.
2) Familiar with Python.
3) The Sqlite description athttp://www.sqlite.org/whentouse.htmlappears to
meet my requirements:
Very low volume and concurrency, small datasets, simple to use.
All good
On Monday, August 27, 2012 10:32:47 PM UTC-4, Bryan wrote:
bruceg113 wrote:
I selected sqlite for the following reasons:
1) Ships with Python.
2) Familiar with Python.
3) The Sqlite description athttp://www.sqlite.org/whentouse.htmlappears to
meet my requirements:
From the sqlite documentation he quoted, it appears that ANY network
filesystem, local or otherwise, should be avoided.
On Aug 27, 2012 8:13 PM, bruceg113...@gmail.com wrote:
On Monday, August 27, 2012 10:32:47 PM UTC-4, Bryan wrote:
bruceg113 wrote:
I selected sqlite for the following
bruceg113 wrote:
Thank you for your reply.
Are you saying having a sqlite database file on a
shared LOCAL network drive is problematic?
Yes, mostly, I think I am saying that.
A LOCAL network drive is network drive, and is not a
local drive, local as the network may be. We read and
write such
My program uses Python 2.6 and Sqlite3 and connects to a network database 100
miles away.
My program reads approx 60 records (4000 bytes) from a Sqlite database in less
than a second.
Each time the user requests data, my program can continuously read 60 records
in less than a second.
13 matches
Mail list logo
