Original issue description
**Describe the bug**
While it is possible to provide a schema with a CamelCase schema id and the correct schema id is stored in the database, listing schemas returns all schema ids in lowercase, such that using a schema id obtained via listing to obtain a single schema will fail.
**To Reproduce**
Steps to reproduce the behavior:
1. Create a schema with id 'MyTest'
2. List all schemas (will contain one schema with id 'mytest'
3. Use 'mytest' to obtain the single schema
4. HTTP 404 is returned
**Expected behavior**
Handling schema ids should be consistent, i.e., either accept CamelCase and return schema ids unchanged in the listing or forbidding CamelCase schema ids.
VolkerHartmann
commented
3 months ago
Original issue description
**Describe the bug** While it is possible to provide a schema with a CamelCase schema id and the correct schema id is stored in the database, listing schemas returns all schema ids in lowercase, such that using a schema id obtained via listing to obtain a single schema will fail. **To Reproduce** Steps to reproduce the behavior: 1. Create a schema with id 'MyTest' 2. List all schemas (will contain one schema with id 'mytest' 3. Use 'mytest' to obtain the single schema 4. HTTP 404 is returned **Expected behavior** Handling schema ids should be consistent, i.e., either accept CamelCase and return schema ids unchanged in the listing or forbidding CamelCase schema ids.closes #547