On Fri, Apr 08, 2005 at 11:01:02PM -0400, Al Danial wrote:
[...]
> What kind of insert performance do you see on your machine? If it
> is substantially better than 120 kinserts/s what kind of hardware
> do you have? I'm especially interested in how much faster the
> code runs on systems with
Al Danial wrote:
The attached C program measures insert performance for populating
a table with an integer and three random floating point values with
user defined transaction size. Usage is:
./sqlite_insert
All of these are on Gentoo, Athlon 64 3200+, running 64 bit.
Writing to /tmp,
Al Danial wrote:
> What kind of insert performance do you see on your machine? If it
> is substantially better than 120 kinserts/s what kind of hardware
> do you have? I'm especially interested in how much faster the
> code runs on systems with multiple disks in a RAID 0 configuration.
> Are
Al Danial wrote:
A scientific application I work with has clumsy data retrieval
options. I dumped the application's output--integer and floating
point numbers--into an SQLite database and soon after began to
enjoy the power of SQL to pull out interesting results.
The main complaint for making the
Random thought: You might squeeze some more performance out by
trying a couple different filesystems. i.e. if you're using ext3,
try some different journaling options, or try ext2.
--- Al Danial <[EMAIL PROTECTED]> wrote:
> A scientific application I work with has clumsy data retrieval
>
A scientific application I work with has clumsy data retrieval
options. I dumped the application's output--integer and floating
point numbers--into an SQLite database and soon after began to
enjoy the power of SQL to pull out interesting results.
The main complaint for making the transfer to
> >
> > select_stmt = db.execute("SELECT * FROM people")
> > # use some, but not all of the rows in select_stmt
> > create_stmt = db.execute("CREATE TABLE other (a,b)") # error:
> > database table is locked
> >
> > Why does this happen?
> >
> > Anyway around
On Apr 8, 2005, at 9:27 AM, Robert Simpson wrote:
Actually if you need to re-use the prepared statement, it's much more
efficient to simply call sqlite_reset() on it instead of finalize.
As long as the statement is not currently step()'ing and is in the
reset
state, the database will not be
> Unable to open database 1.db
> now what? any suggestions?
There's probably nothing you can do to fix the file.
In the past, you could corrupt a database by vacuuming
it in one process and then doing an insert in another
process. This has been fixed in V3; I don't know if the
bug even existed
Actually if you need to re-use the prepared statement, it's much more
efficient to simply call sqlite_reset() on it instead of finalize.
As long as the statement is not currently step()'ing and is in the reset
state, the database will not be locked.
Example:
select_stmt = db.execute("SELECT *
Charles Mills wrote:
I am trying to create a table after creating a select statement
which selects records from an existing table. Is this possible? I
get a SQLITE_LOCKED / "database table is locked" error when I
attempt this.
In psuedo code the logic is as follows:
select_stmt =
On Apr 8, 2005, at 2:35 AM, Paolo Vernazza wrote:
Charles Mills wrote:
I am trying to create a table after creating a select statement which
selects records from an existing table. Is this possible? I get a
SQLITE_LOCKED / "database table is locked" error when I attempt this.
In psuedo code
Hi Cory,
Regarding:
Is there a reason [the sql command] BETWEEN can't use [an index]?
Hmm... nobody has an answer? Or did my message get eaten by a spam filter
:(
I can't answer your question by providing you the reason, but it appears to
be a fact that you will want to use separate
Hi there,
1. i get the following error;
c:\>sqlite.exe 1.db
Unable to open database "1.db": database disk image is malformed
so i can't execute pragma integrity_check.
header: ** This file contains an SQLite 2.1 database **
2. this is the corrupted file:
00: 2A 2A 20 54 68 69 73 20 ? 66
Adam Dziendziel <[EMAIL PROTECTED]> writes:
> SELECT COUNT(*) FROM drzewo_towar WHERE lft > 13 AND rgt < 14 GROUP BY towar
> ...
> the engine doesn't return the value (the above query should return 0).
COUNT(*) returns NULL if there are no records selected. Change the query like
this to
> Hmm... nobody has an answer? Or did my message get eaten by a spam filter
> :(
>
> On Apr 4, 2005 8:02 PM, Cory Nelson <[EMAIL PROTECTED]> wrote:
>> Using the following:
>>
>> create table t_history(time real, ...);
>> create index i_time on t_history(time);
>> select count(*) from t_history
When I execute:
SELECT COUNT(*) FROM drzewo_towar WHERE lft > 13 AND rgt < 14 GROUP BY towar
on the table:
CREATE TABLE drzewo_towar (
id INTEGER PRIMARY KEY,
nazwa TINYTEXT,
towar INTEGER,
lft INTEGER,
rgt INTEGER,
dpt INTEGER
);
INSERT INTO
Hmm... nobody has an answer? Or did my message get eaten by a spam filter :(
On Apr 4, 2005 8:02 PM, Cory Nelson <[EMAIL PROTECTED]> wrote:
> Using the following:
>
> create table t_history(time real, ...);
> create index i_time on t_history(time);
> select count(*) from t_history where time
> Thanks much - one more question though...
>
> I'm attempting to copy data from an in memory database to
> another db (file or otherwise). Is it possible to attach an
> existing in-memory database to another existing db connection?
> (attach database :MEMORY: would just seem to create another
Is it possible for a C application to get a callback as soon as a
database's content has changed?
Best regards,
Frank.
Charles Mills wrote:
I am trying to create a table after creating a select statement which
selects records from an existing table. Is this possible? I get a
SQLITE_LOCKED / "database table is locked" error when I attempt this.
In psuedo code the logic is as follows:
select_stmt =
21 matches
Mail list logo
