Thanks, I understand the issue a bit better now. It looks more like a case of whether the DB system is case-preserving. Sqlite is case-preserving but case-insensitive, whereas pg looks more like case-modifying and case-insensitive (unless identifiers are quoted). Running the mysql server in case-insensitive mode (1) will cause similar problems to pg.
On Monday, 4 December 2023 at 1:07:19 pm UTC+10 Raoul Snyman wrote: > On Monday, December 4, 2023 at 2:20:38 AM UTC Cameron D wrote: > > I don't understand the problem. > My MariaDB server is set to *case-sensitive* (file-system and table > names). The column names are mainly camel case (using a trimmed down > version of the old schema with original names, such as 'inTemp' and 'rain'). > I have a second instance with an ecowitt DB where the column names are > mixed camel and snake (I took standard CamelCase name and added identifying > suffixes with an underscore). And, of course, all the archive table names > are snake with possible camel suffixes, matching the original column name. > > > PostgreSQL is NOT case-sensitive. It converts everything to lowercase in > order to bypass any case sensitivity issues. The problem is that WeeWX is > expecting the database to be case-sensitive. > > -- 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/60bf5fdc-6ece-4d60-b9b6-ba6960f78caan%40googlegroups.com.
