It might be best to not write an archive record less than or equal to the
largest dateTime value in the archive table. Sure, there may be an erroneous
later row, but that is an issue that should be addressed anyway (rather than
ignored). WeeWX already gets the latest at startup (in order to
Over in the WeatherFlow forums a guy had an interesting problem where
occasionally he has timestamps in his weewx.sdb of 300 or so (ie, 12:05AM
1/1/1970 GMT). My 'guess' is his host took a reboot and weewx fired up
before the host had accurate date+time.
Is there an easy way to block writes
