On Tuesday, December 6, 2016 at 9:35:48 AM UTC-5, Graeme wrote: > > Thanks for the reply. I can see that, for maintainers of software in wide > use, this would be a difficult problem to solve. However, as an exercise in > getting to know Python and weewx better, I shall see if I can apply the > changes to the latest release to satisfy my own requirements. > Interestingly, I have been using w1retap (Jonathan Hudson) with a Ruby > presentation program; w1retap interfaces with postgresql, MySQL and sqlite, > and case was not a problem mentioned in the documentation. >
graeme, as tom pointed out, you should start with the weedb shim. that means create a file weedb/postgres.py - i would start with the mysql.py implementation then adjust for postgres. there is a test directory weedb/test that contains unit tests for the database components. simply create a TestPostgres class and you'll quickly see whether your implementation works properly. cd /home/weewx/bin/weedb/test PYTHONPATH=../.. python test_weedb.py as i recall, that is the easy part :) once that works, try saving data to the database by running the simulator. that should be pretty straightforward too. it might get tricky when you get to generating reports... m -- 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.
