Thanks, so more dumb newbie questions...
A single table with a row per archive interval -
"They represent the current conditions as of some time"
So how does WeeWx cope with daily (and greater) records without a separate "daily" table? The temp/wind/whatever could have hit a record value between archive intervals.
I'm coming from Cumulus where it keeps a separate list of all the highs/lows for the current day and at the end of the "day" writes a single row to a daily table recording those highs/lows/averages etc. So how does WeeWX do that?
Sorry this is all a bit theoretical at the moment, but I like to understand how a program works. I have a new pi3 and SSD arriving tomorrow so I can build a system and start to play with it.
I'm also thinking how to drive my web site from a MariaDB; at the moment most of the "archive" type data is pulled from the "daily" table as that is much more efficient than aggregating years of 10 minute data into daily/monthly/yearly. Plus it gets all those transient highs and lows missing from the full archive.
My off the cuff thinking is that I create a daily table myself and add a new row each day via a script. This would mean minimum change to my existing web site scripts. The full archive data extracts I can handle by creating a db view or two to minimise the change there. Realtime type data would be supplied directly by weeWX - again from what I have read so far I think I can create the php variable files required from weeWx skins.
This will be an interesting experiment!
Cheers
Mark