Ah, right! I thought I must be missing something, that why I wanted a schema doc to show all the tables and their relationships. Guess I wait until I get this installed and can have a poke around.
On 22 March 2017 at 19:58, Andrew Milner <[email protected]> wrote: > There is the archive table with one row for each archive interval and > there are the many archive_daily_xxxx tables for the daily highs, lows, > totals per reading type with one row per day. > > Use phpadminlite or phpmyadmin - depending on database you are using - to > look around inside the database and view the structures of each table. > > > > On Wednesday, 22 March 2017 21:51:37 UTC+2, Mark Crossley wrote: > >> 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 >> >> On Wednesday, 22 March 2017 17:40:23 UTC, mwall wrote: >>> >>> On Wednesday, March 22, 2017 at 1:30:53 PM UTC-4, Mark Crossley wrote: >>>> >>>> Dumb question, but I can't seem to find the weeWX database schema >>>> documented anywhere? Am I missing the obvious? >>>> >>> >>> weewx uses the wview schema: >>> >>> http://weewx.com/docs/customizing.htm#archive_types >>> >>> or, more explicity: >>> >>> https://github.com/weewx/weewx/blob/master/bin/schemas/wview.py >>> >>> we have been experimenting with a new, extended schema that will make it >>> easier to use an even wider assortment of hardware: >>> >>> https://github.com/weewx/weewx/blob/schema/bin/schemas/wview-extended.py >>> >>> m >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/weewx-user/aMLZrXWJ_jU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
