Also, i'll try to just document the base and extended schema's to give a good base model. p.s., I'm using Visio as it's the tools i've used for years. If you have a suggestion for another tool, let me know and i'll see if i can load/install/use that tool.
On Saturday, February 27, 2021 at 2:33:01 PM UTC-8 David Prellwitz wrote: > Vince - I did all of that and the schema view is bare, i.e., it's still a > whole lot of nothing other than the field names - and it's not complete > (or even close). I've run a Visio Data Model on Weewx.sdb (my running copy) > and found 114 separate tables; many matching field names. All with the same > PK and little - if any - SK/FK to differentiate what device/station > generated that instance of data. And, all without (relationship) links. All > without documentation or a word anywhere as to what some or most of the > tables are for and/or pertaining to. > > So, rather than slogging through a morass of blogs, texts and various > thousands of pages to try to figure out what most of those tables are for, > i'm okay with adding notes and documentation to my Visio workspace and > publish that info as i complete each piece. I just need people to send me, > or provide links to, any specific documents describing these tables. > Better, if something exists that shows some/most of this info, please > provide it. > > On Thursday, February 25, 2021 at 2:17:50 PM UTC-8 vince wrote: > >> echo ".schema" | sqlite3 mydatabasename.sdb >> >> or look at >> https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py >> for the default schema for current v4 weewx. >> >> On Thursday, February 25, 2021 at 1:48:45 PM UTC-8 david.a....@gmail.com >> wrote: >> >>> Looking through both SQLite and Weewx documentation, i can't find a >>> reference to a tool or report that will take a existing SQLdb and display >>> the underlying DB's structure? I can see that wee-debug will give a listing >>> of fields and key's, but there's no references to the relationships >>> established for the exiting db. I ask because i'd like to understand how >>> the existing data maintains keys. i.e., if data is stored with the only >>> primary key as epoch time, can weewx manage joined keys of epoch+Device-ID? >>> That would allow me to store multiple occurrences of epochDT, but different >>> devices. that would allow me to store data from devices as raw data and >>> data from WF (or other weather services) corrected data concurrently. It >>> would also solve the often-mentioned "What's raw data and what has WF >>> 'conditioned' data in my SQLdb?" issues. >>> /David >>> >>> -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/a4d7e4d2-60bb-48cc-9faa-ee8843699fbfn%40googlegroups.com.
