Hi,
some time ago Richard was involved in http://www.unqlspec.org/ . Is
that still going on? I am quite interested in a backend for sqlite.
thanks,
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listi
Hi,
Recent comment on the topic from unql mailing list:
https://groups.google.com/forum/#!msg/unql/dVc_cM1ZGw8/3QHE1_MIqRQJ
On 04.11.2011 10:50, sqlite-us...@h-rd.org wrote:
Hi,
some time ago Richard was involved in http://www.unqlspec.org/ . Is that
still going on? I am quite interested in a
> If you could use DTrace you could really find out, but since we have
How about something like sysinternals diskmon?
http://technet.microsoft.com/en-us/sysinternals/bb896646
That should give you (OP) some indication of what disk activity
is going on.
Paul.
_
Yuriy Kaminskiy wrote:
> Yuriy Kaminskiy wrote:
>> David wrote:
>>> Simon L wrote 2011-10-25 06:20:
To reproduce this problem, enter the following 5 SQL statements at the
SQLite command line.
create table X(id INTEGER primary key ON CONFLICT REPLACE);
create table Y(id INTE
Thanks. I was afraid of that. I got out my old Data Base Systems books
and was trying to figure out what I forgot. Turns out I didn't forget it.
It's just not possible.
Thanks again. Off to coding.
On Thu, Nov 3, 2011 at 9:08 PM, Pavel Ivanov wrote:
> > What I ultimately want to do is iter
Interesting, I'll give that a try, thanks. Good to know I'm not going crazy...
my worry with this kind of thing is always that my memory management is not
bulletproof and is having a knock-on effect somewhere.
Thanks
Ray
-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:
Hello,
a question from beginner please :
In this transaction (with wal-mode) :
BEGIN TRANSACTION
INSERT INTO
SELECT last_insert_rowid()
COMMIT
Are we sure that another process is not going to create another row between my
"INSERT" and "SELECT LAST ROWID"?
The "LAST ROWID" is it for
On Fri, Nov 4, 2011 at 6:59 PM, Paxdo Presse wrote:
>
> Hello,
>
> a question from beginner please :
>
> In this transaction (with wal-mode) :
>
>
> BEGIN TRANSACTION
>
> INSERT INTO
>
> SELECT last_insert_rowid()
>
> COMMIT
>
>
> Are we sure that another process is not going to create anothe
On Nov 4, 2011, at 11:59 PM, Paxdo Presse wrote:
> Are we sure that another process is not going to create another row between
> my "INSERT" and "SELECT LAST ROWID"?
yes
> The "LAST ROWID" is it for sure the id of "INSERT INTO" of the transaction?
yes
___
Great. Thanks to both.
(and sorry for my bad english)
Le 5 nov. 2011 à 00:05, Petite Abeille a écrit :
>
> On Nov 4, 2011, at 11:59 PM, Paxdo Presse wrote:
>
>> Are we sure that another process is not going to create another row between
>> my "INSERT" and "SELECT LAST ROWID"?
>
> yes
>
>>
Have a database and an application wherein , concurrent writes and reads
to/from the db happen (each DB connection is independent , autocommit mode
and no SQLITE_BUSY handler / timeout ).
I see "Database is locked" message.
Is there a good practice /setting for such high rate of concurrent write
On 5 Nov 2011, at 3:32am, swamir wrote:
> Will a busy_timeout setting for all connections and making write
> transactions as "begin immediate" handle the situation ?
First, just try just setting a timeout and see if that fixes the problem.
http://www.sqlite.org/c3ref/busy_timeout.html
Simon.
12 matches
Mail list logo