There are some other places in the code that are database-dependent. In particular, look at the queries in weewx/xtypes.py, dictionary "group_defs". Maybe you can figure out a way around that.
Thanks for the pointers, I'll take a look. I don't think the lookup table you supplied in postgres.py will survive the test of time. There are just too many types out there in the wild to ever capture them in a static structure. Whenever you create a table, I think it will be necessary to save the original names in database metadata, then return that when needed. Yeah, it's not ideal, it's really just a workaround. I created the list by combining the column names from the 3 schemas, and any time a new schema is created the lookup table would need to be modified. Saving the column names in the metadata sounds like it may work, I'll play around with that idea. Make sure you don't drift too far away from the V5 code. I don't see any major refactoring coming up, but I can't guarantee it either. Yup, I'm rebasing on the V5 branch fairly often. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/102269ca-f298-493b-975d-843f4c1d465bn%40googlegroups.com.
