Potntial issue with table name resolution

[hiltontj]

Problem statement

There may be an issue with case sensitivity in table name resolution.

Steps to reproduce

Perform the following set of writes

influxdb3 write --database test \                  
'airSensors,sensor_id=100 temperature=71,humidity=35,co=0.5098 1732669098000000000
airSensors,sensor_id=101 temperature=71,humidity=34,co=0.5034 1732669098000000000
airSensors,sensor_id=102 temperature=71,humidity=34,co=0.5175 1732669098000000000'

Then query the resulting table:

influxdb3 query --database=test "SELECT * FROM airSensors LIMIT 10"

This should result in the following error:

Query command failed: server responded with error [500 Internal Server Error]: query error: error while planning query: Error during planning: table 'public.iox.airsensors' not found

The error indicates that the lowercase airsensors table does not exist.

Performing a SHOW MEASUREMENTS indicates that the table is there, but with the camelCase name airSensors, i.e., as it was in the written line protocol.

influxdb3 query --database=test --language=influxql "SHOW MEASUREMENTS"
+------------------+------------+
| iox::measurement | name       |
+------------------+------------+
| measurements     | airSensors |
+------------------+------------+

Proposed solution

1. Create a test to reproduce this behaviour
2. Investigate and see if fixing the issue is easy or expand on this issue with more context

[pauldix]

I think table names are supposed to be case sensitive? I'm not sure, I can't remember what the 1.x and 2.x behavior was, but I thought it was.