I'll be merging the V5 branch into the development branch in the next few days, but target the V5 branch for now.
As I recall, the "case sensitivity" problem with Postgres is that in order to achieve case-insensitivity, it converts *everything* to lower case, including column names. When WeeWX starts up, it reads the schema from the database itself. So, something that started out like "outTemp" becomes "outtemp". Then if some code needs the outside temperature to calculate, say, dewpoint, it can't find it because Python string comparisons are always case-sensitive. In the intervening years, perhaps Postgres has added a switch to prevent this. Don't know. To work around it in the WeeWX code would require either that all string comparisons involving SQL types become case-insensitive, which would break countless 3rd party extensions, or the code that reads the schema from the database would have to be changed to read it from metadata, or someplace else. There are ways around the problem. But, it's a biggish project. I'd be mighty grateful if someone took it on. -tk On Saturday, December 2, 2023 at 7:46:32 PM UTC-8 Raoul Snyman wrote: > Hello, > > I just came across WeeWX a week or so ago when I was looking for some open > source Linux-based software to pull data from my AcuRite weather station. > Fantastic project. > > I am working on adding support for PostgreSQL (my database of choice), and > I wanted to check which branch I should be targeting. I see the V5 branch, > which seems to be the future of WeeWX, but the docs specify targeting the > "development" branch. > > Thanks! > -- 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/9af547f0-449a-4c79-96b4-2f3559359232n%40googlegroups.com.
