> On Oct 20, 2019, at 12:53 AM, Thomas Kurz wrote:
>
> many "playground" gadgets keep being implemented (like virtual columns,
> virtual tables, FTS3/4/5, ...),
I suspect you are used to database servers, and haven’t used SQLite as an
embedded library inside an app (its primary use case.)
On Sunday, 20 October, 2019 06:58, Petr Jakeš wrote:
>On Sun, Oct 20, 2019 at 2:53 AM Keith Medcalf wrote:
>> On Saturday, 19 October, 2019 18:26, Petr Jakeš
>> wrote:
>>> After long time I have set up development environment properly and I
>>> am able to start to study your queries.
>>>
On Sun, Oct 20, 2019 at 4:36 PM Keith Medcalf wrote:
>
> On Sunday, 20 October, 2019 06:58, Petr Jakeš
> wrote:
>
> >On Sun, Oct 20, 2019 at 2:53 AM Keith Medcalf
> wrote:
>
> >> On Saturday, 19 October, 2019 18:26, Petr Jakeš <
> petr.jakes@gmail.com> wrote:
>
> >>> After long time I have
This is getting far away from SQLite now and moving to medical statistics.
The thing is that the authors of this algorithm have taken a large amount
of patient
data and have calculated what the best predictors are to calculate the
chance for the
individual patient to have a heart attack or stroke
On Sun, Oct 20, 2019 at 8:23 PM Petr Jakeš wrote:
>
>
> On Sun, Oct 20, 2019 at 4:36 PM Keith Medcalf wrote:
>
>>
>> On Sunday, 20 October, 2019 06:58, Petr Jakeš
>> wrote:
>>
>> >On Sun, Oct 20, 2019 at 2:53 AM Keith Medcalf
>> wrote:
>>
>> >> On Saturday, 19 October, 2019 18:26, Petr Jakeš
Interesting! I appreciate the detailed response. I don't think the shadow table
digging fits our risk profile exactly :), but it's interesting to know where to
look if we want to check ourselves. I realized after rereading all of this that
ultimately we want to keep track of the max rowid
On Sun, 20 Oct 2019 at 17:04, Simon Slavin wrote:
> Another common request is full support for Unicode (searching, sorting,
> length()). But even just the tables required to identify character
> boundaries are huge.
>
Nitpick: there are no tables required to identify character boundaries. For
Rowan, you're talking about Unicode codepoints; however, Unicode graphemes, what
typical humans consider to be characters, are sequences of 1..N codepoints,
example a letter plus an accent that get composed together, and this is what
takes those large tables; this is related to Unicode Normal
On Oct 20, 2019, at 9:20 PM, Darren Duncan wrote:
>
> Rowan, you're talking about Unicode codepoints; however, Unicode graphemes,
> what typical humans consider to be characters, are sequences of 1..N
> codepoints, example a letter plus an accent that get composed together, and
> this is what
On 20 Oct 2019, at 1:54am, Peng Yu wrote:
> How to prove the large time difference of sqlite3 is indeed due to
> cache and where is the cache?
Keep the database on an external drive (e.g. USB Flash drive). Unmount the
drive to be sure that the cache has been cleared.
> Why the caching used
On 2019-10-20 12:53 a.m., Thomas Kurz wrote:
I'd kindly ask whether there is some sort of roadmap for SQLite development?
Someone recently pointed out how much he loves the "lite" and well-thought features. I cannot see
that: I observe that many "playground" gadgets keep being implemented
Thanks for that and have tried this now (on Android app) and works fine.
It is fast as well, although slightly slower than the previous version.
I ran this on a column with 8000 values ranging from 0 to 1600 and this
took about 140 milli-seconds
on a fast Samsung S9 phone. Database is on a SD.
I
I'd kindly ask whether there is some sort of roadmap for SQLite development?
Someone recently pointed out how much he loves the "lite" and well-thought
features. I cannot see that: I observe that many "playground" gadgets keep
being implemented (like virtual columns, virtual tables, FTS3/4/5,
On 19/10/62 06:31, Ben Asher wrote:
Hello! I'm trying to write some code to keep an external content table in
sync with the index. To do this, I need to be able to get some state about
the index: either how many rows have been inserted so far or the max rowid
that has been inserted into the
On 20 Oct 2019, at 8:53am, Thomas Kurz wrote:
> I'd kindly ask whether there is some sort of roadmap for SQLite development?
Only private to the developers, probably just mentioning whatever they're
worried about at the moment. Nothing public.
> Someone recently pointed out how much he loves
> You can try clearing Linux file system cache to convince
> yourself that cache misses contributes to performance drop.
>
> Run this as root:
>
> # sync; echo 3 > /proc/sys/vm/drop_caches
I am on Mac OS X. Is there anything equivalent? Thanks.
--
Regards,
Peng
On 20/10/62 14:53, Thomas Kurz wrote:
I'd kindly ask whether there is some sort of roadmap for SQLite development?
Someone recently pointed out how much he loves the "lite" and well-thought features. I cannot see
that: I observe that many "playground" gadgets keep being implemented (like
Another approach is to question whether you really need the
standard deviation or if any measure of variation would do.
You could use the range, max(x) - min(x) , and just report it as the range
rather than the standard deviation. Also range/4 approximates the
standard deviation (google the
On 20 Oct 2019, at 12:36pm, Peng Yu wrote:
> I am on Mac OS X. Is there anything equivalent? Thanks.
Have the database stored on a Flash Drive. Eject (or unmount) the Flash Drive.
Works on all versions of all operating systems.
___
sqlite-users
Yes, could use something else than SD, but the mentioned calculator uses SD.
Got this all working fine now.
RBS
On Sun, 20 Oct 2019, 13:31 Gabor Grothendieck,
wrote:
> Another approach is to question whether you really need the
> standard deviation or if any measure of variation would do.
>
>
On Sun, Oct 20, 2019 at 2:53 AM Keith Medcalf wrote:
> On Saturday, 19 October, 2019 18:26, Petr Jakeš
> wrote:
>
> >After long time I have set up development environment properly and I am
> >able to start to study your queries.
>
> >I am lost. I don't either understand the first bunch of
In my experience max(x) - min(x) isn't a great measure for this sort of
thing, as it is ultimately dependent on outliers. Something like
75%-tile to 25%-tile (or other similar values) might make more sense.
Ultimately, taking a Standard Deviation (or Variance) of a set of
reading for a set of
22 matches
Mail list logo
