Perhaps an analogy will help: Imagine you are given a piano. Pressing keys on
the piano will cause the corresponding tones to be played. If you hit the keys
on the piano with a hammer, then this too will cause tones to be played;
however, it will also most likely cause mechanical failure (i.e.
Thanks for taking the time to send in the report and thanks to all who
investigated it. The robust discussion demonstrates the passion of the sqlite
community, and I enjoy thinking about the various points as they are made.
From: [Vermes Mátyás
> On Mar 8, 2017, at 12:52 PM, R Smith wrote:
>
>> Interestingly I rarely see dates stored in ISO8601 format/text
>
> Because every programmer is a self-proclaimed optimization genius!
In this case it often makes sense to optimize in advance. In multiple
situations over
On 10 Mar 2017, at 2:05pm, Anthrathodiyil, Sabeel (S.)
wrote:
> Stack trace is as below
> --
> pcache1RemoveFromHash
> pcache1EnforceMaxPage
> pcache1Shrink
> sqlite3PcacheShrink
>
> The sequence of SQLite operations being followed which lead
On 3/10/17, Anthrathodiyil, Sabeel (S.) wrote:
> Hi,
> I am facing a crash while invoking "sqlite3_db_release_memory" the crash is
> from pcache1RemoveFromHash. SQLite 3.7.10 is running on ARM A5 with
> Freescale MQX as OS.
>
> Any probable reasons in term of the SQLite
> On Mar 9, 2017, at 7:55 AM, Keith Medcalf wrote:
>
> Why are you using SHARED_CACHE since it does not sound like you have memory
> constraints on cache size, which is the primary (only) reason you would ever
> want to use shared cache since the penalties for doing so
Hi,
I am facing a crash while invoking "sqlite3_db_release_memory" the crash is
from pcache1RemoveFromHash. SQLite 3.7.10 is running on ARM A5 with Freescale
MQX as OS.
Stack trace is as below
--
pcache1RemoveFromHash
pcache1EnforceMaxPage
pcache1Shrink
On Friday, 10 March, 2017 10:57, Jens Alfke wrote:
>> On Mar 9, 2017, at 7:55 AM, Keith Medcalf wrote:
>> Why are you using SHARED_CACHE since it does not sound like you have
>> memory constraints on cache size, which is the primary (only) reason you
>>
On 10 Mar 2017, at 9:34pm, Keith Medcalf wrote:
> You mean physical reads? I suppose this would be possible, as long as the
> working set of all your read queries are able to fit in the cache
> simultaneously. If not, you are likely to get more cache thrash with the
>
> On Mar 10, 2017, at 3:32 PM, Simon Slavin wrote:
>
> Two different patterns of use. One is that the different threads/processes
> usually care about different rows (maybe in different tables). In that case,
> shared cache is of very little benefit. The other is when
On 10 Mar 2017, at 9:34pm, Keith Medcalf wrote:
> You mean physical reads? I suppose this would be possible, as long as the
> working set of all your read queries are able to fit in the cache
> simultaneously. If not, you are likely to get more cache thrash with the
>
On 3/10/17, Dominique Devienne wrote:
>
> PS: The latter would be better than nothing (I mean in compiled ready to
> use form),
> if the former doesn't happen, as seems likely given the lack of response
> from DRH.
> (via the ML or the SQLite Fossil Timeline)
The SQLite
> With 3.11.0, the scan is probably using the index instead of the table
In this case the phenomena would be a new "feature". Unfortunately this would
contradict to the axiom, that the result of a query must be independent of the
existence of the indices.
--
Vermes Mátyás
Thanks. Naturally I had experimented with several versions of the program, and
saw that any ordering makes the new feature/error disappear. You can see it if
you read the comment at the bottom of my original script. But my purpose was
the opposite: demonstrate the regression. I am not
On Wednesday, 8 Mar 2017 3:40 PM -0500, Paul Sanderson wrote:
> The vast majority of dates I see in SQLite databases are unix epoch integer
^
> times (seconds since 1/1/1980) with unix milli seconds a close second.
^
> Efficient to store, sort and do date
Documentation suggests that -DSQLITE_THREADSAFE has 3 valid values: 0,
1, 2. https://www.sqlite.org/threadsafe.html
But configure script appears to only be able to set the values 0 and 1
with --enable-threadsafe. How to set -DSQLITE_THREADSAFE=2? I think,
configure script is missing this
There is extension-functions.c in
http://sqlite.org/contrib/download/
which I (and probably others) use, works well, gets via my .sqliterc always
loaded.
This extension-functions.c is a bit hard to find, probably because of its
not so descriptive name. It is not standalone, rather it links to
On Fri, Mar 10, 2017 at 12:29 PM, Stephan Buchert
wrote:
> There is extension-functions.c in
> http://sqlite.org/contrib/download/
> [...]
Is the suggestion to have sqrt, sin, cos, stdev, ... built into sqlite
> standalone, or to provide a more a obvious way to access the
18 matches
Mail list logo