I'm working with version 3.5.2 under Linux. I've got a database that
is being shared between two processes and I'm running into issues with
the journal file that doesn't go away. When that happens, one process
appears to have the lock on the database and the other process is
essentially locked
I guess the other thing I should add is that we're using Qt/Qtopia.
In theory, it shouldn't matter, but, I thought I'd mention it just in
case.
Mark
On 1/21/08, James Dennett <[EMAIL PROTECTED]> wrote:
> (Top-posting and overquoting fixed.)
>
> On Monday, January 21, 2008 1:57
I'm just executing SQL insert statements. I'm not using the BEGIN
TRANSACTION; ... END TRANSACTION; wrappers around the inserts.
I thought that there was an implied BEGIN ...COMMIT around every
INSERT statement?
Mark
On Jan 21, 2008 4:48 PM, Igor Tandetnik <[EMAIL PROTECTED]> wrote:
I'm running version SQLite 3.5.2 under Linux on a small ARM processor
with a flash drive.
I've got a single-threaded C++ process that inserts data into an
SQLite database, and a series of PHP (v5.2.4) scripts using PDO that
insert to and read from the same database. In terms of the
percentages,
Is there a way to merge these in such a way that I could make this
from a system call? For example, let's say I want to create this dump
file from a Perl or shell script using a system call. Can I do that?
Thanks,
Mark
On Jan 15, 2008 4:59 PM, Rich Shepard <[EMAIL PROTECTED]> wrote:
> On Tue,
I'm coming from a MySQL background and the mysqldump utility supports
schema-only, data-only, and schema plus data dumps. I thought that
there was an SQLite trick I was missing somewhere.
Mark
On Jan 15, 2008 4:10 PM, Rob Sciuk <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 15 Jan 2
Is there a way to dump out the contents of the database w/o having the
CREATE TABLE statements? For example, I can do the following:
sqlite3 foo.db .dump > foo.dmp
However, foo.dmp contains all of the CREATE TABLE statements. I just
want all of the INSERT INTO statements associated with this
I'm running SQLite 3.4.1 under Linux. I have a C++ application that
inserts records into the database.
During testing, I lauch the C++ app and I start sqlite3 from a console
and open the database that is being written to by the C++ application.
I perform selects using sqlite3 (no inserts) to
All - We're in the process of porting an application that used MySQL
to an embedded platform running SQLite. Two of the built-in functions
we used frequently were the functions to create and convert from Unix
epochs (UNIX_TIMESTAMP(), FROM_UNIXTIME).
Are there any plans to add this functionality
I'm developing an application to run on an ARM-based PDA-like device.
It's running Linux and I've got SQLite 3.4.1 installed.
I'm trying to optimize my insert statements (in a different discussion
thread) I've gotten some good suggestions to use the PRAGMA statement
to disable the syncronization.
MIT;";
Is this the correct syntax for the PRAGMA statement? Can I issue it
once and will it remain active as long as the connection is open?
Thanks,
Mark
On Dec 3, 2007 6:45 PM, Mark Riehl <[EMAIL PROTECTED]> wrote:
> I used the PRAGMA statement and turned off the synchronous optio
I used the PRAGMA statement and turned off the synchronous option. It
made a huge difference. Single inserts were ranging from 5 - 50 ms,
now, they're at ~.04 ms.
However, I guess there is a tradeoff between the safety of the
synchronous operation (in case power is lost) versus the insert
;
> for (0 .. 99) {
> $str .= ('a' .. 'z')[int(rand(25)) + 1];
> }
> return $str;
> }
>
> timethis(1000, \);
>
> $ ./db.pl
> timethis 1000: 2 wallclock secs ( 0.20 usr + 0.75 sys = 0.95 CPU) @
> 1052.63/s (n=1000)
>
>
> On 12/3/07, Ma
I've got an application that logs real-time data. Some of the data is
periodic (every few secs), other data comes more frequently.
Basically, I'm not dealing with bulk inserts, so, I can't queue things
up and insert all at once.
I'm noticing that my insert times are pretty slow (~5-50 ms on a
14 matches
Mail list logo
