On 14.09.2016 13:31 Dan Kennedy wrote:
> On 09/14/2016 06:05 PM, Martin Raiber wrote:
>> there have been three reports by users using my software of SQLite
>> 3.12.0 returning SQLITE_IOERR and logging a SQLITE_IOERR_SHORT_READ
>> (522). Specifically:
>>
>> 2016-09-12 04:37:04: WARNING: SQLite:
On 14 Sep 2016, at 1:09pm, Martin Raiber wrote:
> I'd expect corruptions to affect sqlite3_step as well and earlier. This
> IO error only occurs for sqlite3_prepare_v2.
Because you have posted an error which can result from a corrupted database, it
is definitely worth
On 14/09/2016 9:23 PM, Clemens Ladisch wrote:
David Crayford wrote:
How do I do something similar to DB2 decimal() function which will add trailing
zeros to precision?
You could use the standard SQL CAST() to convert the value back into a number,
by why not simply sort by the original
Hi,
there have been three reports by users using my software of SQLite
3.12.0 returning SQLITE_IOERR and logging a SQLITE_IOERR_SHORT_READ
(522). Specifically:
2016-09-12 04:37:04: WARNING: SQLite: disk I/O error errorcode: 522
2016-09-12 04:37:04: ERROR: Error preparing Query [PRAGMA cache_size
Greetings,
I've just started using sqlite to (ironically) report on z/OS DB2 stats.
I've written a query where the results look a bit strange. I group by
the DB2 plan name and order by the maximum
CPU time. The sort order looks incorrect as you can see in the report
below. I'm certainly not
David Crayford wrote:
> How do I do something similar to DB2 decimal() function which will add
> trailing zeros to precision?
You could use the standard SQL CAST() to convert the value back into a number,
by why not simply sort by the original number to begin with?
ORDER BY max(cpu1)
On 14 Sep 2016, at 11:57am, SinhaK wrote:
> create table 'Stream0' ( TokenNo int NOT NULL,OrderId integer NOT NULL,SIDE
> int NOT NULL,PRICE int NOT NULL,QTY int NOT NULL,PRIMARY KEY (OrderId));
>
> Index On Table :
>
> CREATE INDEX DataFilterIndex ON
Hello SinhaK,
>>I decided to use sqlite3 in c++ after reading a lot about its
>>performance.
If it's purely in memory, I question why you're using Sqlite in the
first place. I'd use in memory data structures like a hash set or
multi-map instead.
Sqlite is great and I use it a bunch but
On 14.09.2016 13:26 Simon Slavin wrote:
> Check the hard disk format for format errors (fsck).
>
> Run "PRAGMA integrity_check" on the database file.
>
> Is the database file on a disk inside the computer running the SQLite calls,
> or is it accessed across a network ?
>
> Do you use any PRAGMAs
Thanks Scott for that explanation.
John
On 11/09/2016 01:27, Scott Robison wrote:
On Sep 10, 2016 2:54 AM, "John McMahon" wrote:
On 08/09/2016 10:09, Bob McFarlane wrote:
Please reply if you sent this. Thanks.
Hmm, looks like a fishing exercise to me. Same
On 14 Sep 2016, at 12:05pm, Martin Raiber wrote:
> there have been three reports by users using my software of SQLite
> 3.12.0 returning SQLITE_IOERR and logging a SQLITE_IOERR_SHORT_READ
> (522).
Check the hard disk format for format errors (fsck).
Run "PRAGMA
On 14 Sep 2016, at 2:10pm, Clemens Ladisch wrote:
> The sort order of these strings looks correct.
Heh. Heh heh.
Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
Of course. How do I do something similar to DB2 decimal() function which
will add trailing zeros to precision? I tried round(col,6) but it
knocked off the trailing zero like 12.12345.
On 14/09/2016 9:10 PM, Clemens Ladisch wrote:
David Crayford wrote:
9.733366
595.509361
29.117646
28.607606
On Wed, Sep 14, 2016 at 3:10 PM, Clemens Ladisch wrote:
> The sort order of these strings looks correct.
>
As hinted by Clemens, you're sorting text values, not reals. See below. --DD
C:\Users\ddevienne>sqlite3
SQLite version 3.10.2 2016-01-20 15:27:19
Enter ".help" for
On 09/14/2016 06:05 PM, Martin Raiber wrote:
Hi,
there have been three reports by users using my software of SQLite
3.12.0 returning SQLITE_IOERR and logging a SQLITE_IOERR_SHORT_READ
(522). Specifically:
2016-09-12 04:37:04: WARNING: SQLite: disk I/O error errorcode: 522
2016-09-12 04:37:04:
I am stuck in a issue related to slow sqlite3 select. I have searched a
lot on this forum and have applied many of the suggestion which has
somewhere helped me in moving ahead. I assume there are some fault in
the way i am trying to use sqlite or may be the settings which i have
used while
David Crayford wrote:
> 9.733366
> 595.509361
> 29.117646
> 28.607606
> 14.684294
The sort order of these strings looks correct.
Regards,
Clemens
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
> Behalf Of Igor Tandetnik
> Realize that a transaction is a property of a connection, not a thread or a
> query. Suppose thread A starts a read at time T and ends it at time
> T+20; and thread B starts a read on
On 14 Sep 2016, at 4:49pm, Alex Ward wrote:
> In my original post I said we had done that and it didn’t help, but we just
> locked the step, not the prepare/step/finalize so I'm guessing if we lock all
> three we will be ok.
It is not enough to lock the _prepare, lock the
I think this is answered, but since you are a bit new to SQLite, and to
be somewhat more informant...
On 2016/09/14 3:19 PM, David Crayford wrote:
Of course. How do I do something similar to DB2 decimal() function
which will add trailing zeros to precision? I tried round(col,6) but
it knocked
> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
> Behalf Of Simon Slavin
> It is not enough to lock the _prepare, lock the _step()s, and lock the
> _finalize.
> If they're sharing a connection with other threads then the lock has to be
> placed at the start of
> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
> Behalf Of Hick Gunter
> Sharing a connection between threads makes it practically impossible for any
> one thread to tell when a transaction begins or ends. From the point of view
> of the database connection, the
> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
> Behalf Of Simon Slavin
> Your description of your fault suggests that at least two of your
> threads/processes are trying to use the same connection to the database at
> the same time
We have a bunch of reads
> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
> Behalf Of Igor Tandetnik
> Statement execution starts with the first sqlite3_step after sqlite3_prepare
> or the most recent sqlite3_reset; and ends with sqlite3_reset or
> sqlite3_finalize.
Thanks makes sense.
> Le 14 sept. 2016 à 18:14, Alex Ward a écrit :
>
> I don't think we can afford to have a connection per thread. We have an
> arbitrarily large number of threads coming and going all the time and a
> combination of the amount of memory each connection is taking up and how
On 9/14/2016 11:49 AM, Alex Ward wrote:
Just to clarify, when you talked about 'starting' and 'ending' a read
can I take that to mean the time between sqlite3_prepare and
sqlite3_finalize?
Statement execution starts with the first sqlite3_step after
sqlite3_prepare or the most recent
> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
> Behalf Of Olivier Mascia
> If I'm permitted: you're wrong.
Ha, yes, well if our initial threading model is anything to go by, I think
you're on safe ground with that assertion.
> Unless you have a very complex
> On 14 Sep 2016, at 5:47pm, Alex Ward wrote:
>
>> Behalf Of Simon Slavin
>
>> It is not enough to lock the _prepare, lock the _step()s, and lock the
>> _finalize.
>> If they're sharing a connection with other threads then the lock has to be
>> placed at the start of the
On 14 Sep 2016, at 7:29pm, Alex Ward wrote:
> Perhaps our schema needs a rework, would one table with a million rows be
> better than 500 tables with 2000 rows each?
Yes. As a guideline, if two tables have the same columns (or even nearly the
same columns) you should
Alex,
> Le 14 sept. 2016 à 20:29, Alex Ward a écrit :
>
>> Unless you have a very complex schema (I would say at the very least more
>> than on hundred tables and other create statement), opening a SQLite
>> connection is lightweight,
>
> We currently have 500 tables and
AFAIK there is no "write mark" in the WAL journal. Instead, each read
transaction (either implicit or explicit) has an associated "read mark" that
determines which data the transaction will see (i.e. the data from the main
file plus any pages in the WAL journal file before the read mark). This
System.Data.SQLite version 1.0.103.0 (with SQLite 3.14.2) is now available
on the System.Data.SQLite website:
https://system.data.sqlite.org/
Further information about this release can be seen at:
https://system.data.sqlite.org/index.html/doc/trunk/www/news.wiki
Please post on the
32 matches
Mail list logo