Thanks, Gary.  It's getting late. so I'll try this in the morning.  Once 
again, thanks for your help!

On Wednesday, January 24, 2018 at 10:07:04 PM UTC-8, gjr80 wrote:
>
> Some answers below, as usual it's not just a simple yes/no.
>
> Gary
>
> On Thursday, 25 January 2018 15:41:48 UTC+10, loonsailor wrote:
>>
>> If I am to modify /etc/weewx/weewx.conf, I should stop weewx, back up 
>> weewx.conf, make the changes you suggest to it, and run wee_database.
>>
>
> Normal rule of thumb is that if you make changes to weewx.conf you need 
> to stop/start weeWX for the changes to take effect. That is true for weeWX, 
> but in this case we are running wee_database which will be run as a 
> completely separate process to weeWX. Also, since wee_database will only 
> be accessing your wview_archive_fixit.sdb database, weeWX could continue 
> to run and wee_database could be run on wview_binding and there would be 
> no database contention (assuming of course that weeWX is running using a 
> binding other than wview_binding for storing archive data). So chances 
> are you could leave weeWX running. I would play it safe though and stop 
> weeWX while running wee_database. 
>  
>
>>   If all goes as planned, I will then have a fixed archive, which I can 
>> go ahead and combine with my existing weewx archive (I've been running it 
>> for about a month now), put it in place, go back to the backed up .conf 
>> file, and restart weewx.  Is that right?
>>
>
> By way of 'backed up .conf file' do you mean mean weewx.conf as it was 
> before you added the wview binding? If so it does not matter, there is no 
> need to revert to a backed weewx.conf just becasue you added the wview 
> binding and now want to revert your weewx.conf. You can have dozens of 
> bindings defined in weewx.conf and weeWX will only use the one you define 
> at the data_binding config option in [StdArchive] for saving archive data 
> (you may well have other extensions installed that may use other bindings 
> for accessing data in other databases but these woudl be defined elsewhere) 
>
> But yes after running --fix-strings on your wview data you should have an 
> archive that you can merge with your weeWX data, of course providing that 
> the problem with your wview data was in fact null strings in numeric fields.
>
>
>> BTW, what does weewx do when there are multiple databases defined in 
>> .conf?  If I leave the existing archive, and add the new one as 
>> wview_archive_sqlite, what does that mean to weewx?
>>
>
> I guess the above comment already answered this, weeWX doesn't care about 
> unused bindings/databases defined in weewx.conf, weeWX only uses those it 
> is told to use any others are ignored. So leaving the existing archive data 
> binding ([[wx_binding]] I expect) and the new one will not be a problem, 
> the only issue is a cosmetic one of housekeeping; after doing this numerous 
> times (for whatever reason) you might end up with a lot of unused, 
> confusing junk in weewx.conf.
>  
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to