Post by impactoz on Aug 10, 2019 18:44:10 GMT -8
Fresh install of v42 found another issue...
The WeatherPiStructure.sql has listed the following;
CREATE TABLE `Sunlight` (
`ID` int(11) NOT NULL,
`TimeStamp` datetime NOT NULL,
`Visible` int(11) NOT NULL,
`IR` int(250) NOT NULL,
`UV` int(250) NOT NULL,
`UVIndex` float NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
Notice that it has no auto increment, primary key or other definitions found in the other tables.... Which results in an error running SkyWeather relating to the ID field not having any value....
Argghhh…..
It stops saving data into Sunlight as well as weather data as the error gets trapped and the data is not committed.
The WeatherPiStructure.sql has listed the following;
CREATE TABLE `Sunlight` (
`ID` int(11) NOT NULL,
`TimeStamp` datetime NOT NULL,
`Visible` int(11) NOT NULL,
`IR` int(250) NOT NULL,
`UV` int(250) NOT NULL,
`UVIndex` float NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
Notice that it has no auto increment, primary key or other definitions found in the other tables.... Which results in an error running SkyWeather relating to the ID field not having any value....
Argghhh…..
It stops saving data into Sunlight as well as weather data as the error gets trapped and the data is not committed.
