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š
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
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 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
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 subqueries... (
>What is returned in the "ratetoprior"? I have been
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 subqueries... (
What is returned in the "ratetoprior"? I have been pulling my hair over 3
hours trying to figure it out ... no clue
On Monday, 2 September, 2019 12:26, Petr Jakeš wrote:
>Yes, you are right. The error is connected with the version of
>SQLite. Now I am trying to build DB Browser using SQLite version 3.29.0.
>Than I have to study your code. Your knowledge and SQL Windows
>functions are over my scope. Thank
Yes, you are right. The error is connected with the version of SQLite. Now
I am trying to build DB Browser using SQLite version 3.29.0.
Than I have to study your code. Your knowledge and SQL Windows functions
are over my scope. Thank for the study material for next weekend :D
On Mon, Sep 2, 2019
On Monday, 2 September, 2019 10:34, Petr Jakeš wrote:
>Wow, this is HUUUDGE !!!
>Thanks!
>What editor are you using, btw?
Typically this is on Windows 10 (for Workstations) and the editor I use is TSE
(The Semware Editor). Started using TSE under OS/2 way back and I like it a
lot and have
Wow, this is HUUUDGE !!!
Thanks!
What editor are you using, btw? I am on Linux Mint and trying your queries
with "SQLite Studio" and "DB Browser for SQLite" is throwing syntax error
(I think because of the rows
"lead(timestamp) over (order by timestamp) as next_timestamp,"
From the sqlite3
Of course, what we are emulating here is called a "Process Historian", common
examples being PHD and PI. So, if you make a few minor adjustments, you can
make this run just about as fast as a "designed for purpose" Process Historian.
The changes are that you need to store the data in an
This will get you the consumption projection for each day in the table
(timestamp in s represents the ENDING period you are interested in and you can
modify it to whatever interval you want, and of course the final query gets the
result). It works by computing the slope from each timestamp to
As far I have ended with following:
WITH miniPow as (
select date(TIMESTAMP,'+1 day') as d, max(TOTAL_KWH) mini
from power
group by date(timestamp)
)
, maxiPow as (
select date(TIMESTAMP) as d, max(TOTAL_KWH) maxi
from power
group by date(timestamp)
)
select maxiPow.d, ROUND(maxi-mini, 1) from
I am storing electricity consumption data to the sqlite.
The simple table to store kWh consumption looks like following example
(accumulated total readings in each row - exactly as you see on your
electricity meter):
|ID|timestamp|kWh ||1 | 2019-07-31 14:24:25 | 270.8||2 |
14 matches
Mail list logo
