I wonder if you've managed to get a duplicate timestamp?

select datetime(dateTime, 'auto'), count(*) from archive group by 1 having 
count(*) > 1;

On Tuesday, 24 December 2024 at 05:17:40 UTC mihec wrote:

> Hi,
> I then used a desktop PC to do database update (which went much faster) 
> but it fails with same error at same timestamp. I also tried with 
> drop-daily and rebuild-daily options but it failed at same timestamp, too.
> I think there must be an invalid entry in my database (Aug 12, 2021). My 
> SQLite database management knowledge is basically zero, so I'm looking for 
> advice how to transfer portions of my database (e.g. from-to specific 
> dates) to a fresh database. This way I'd avoid invalid dates (I hope?).
> For the new database I'd like to add at least one new column where I keep 
> some specific data (lightning strikes) and copy it from my original one.
> Keeping in mind I started a fresh (temporary) database yesterday, I hope 
> to add this latest data, too - if possible.
>
> Thank you for your instant help so far, I really appreciate.
>
>
> torek, 24. december 2024 ob 01:58:11 UTC+1 je oseba Graham Eddy napisala:
>
>> a few years ago i struck a case in weewx where a mass database update was 
>> taking many, many hours to run in test environment - too long for live 
>> database - seemed to be a weird i/o bottleneck corner case.
>> my solution was to move the database to ram disk (symlink’ed to minimise 
>> weewx config changes), complete the update, then move it back - execution 
>> time a few minutes.
>> *⊣GE⊢*
>>
>> On 24 Dec 2024, at 6:46 am, mihec <pete...@gmail.com> wrote:
>>
>> It seems it will take several hours to finish (takes 1 minute for 25 days)
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/25b3dd31-7503-4784-81ff-155c6c2fe61an%40googlegroups.com.

Reply via email to