Currently the SQLite, Spatialite and Geopackage Writers (all SQLite based) enforce constraints on table and column names that do not align with the format specifications.
For example, all formats allow Upper Case characters, spaces etc. within Table Names and Column Names, with only limitations that have to begin with an alphabetic character and certain SQLite Reserved words cannot be used without enclosing the field name in “”.
In order to maintain Schema alignment between Eg. a Data Source, like a Geodatabase, SQL Server etc. that may contain Upper Case characters, spaces etc. then the corresponding SQlite based formats above should, by default, keep the Schema Attribute Names as-is, since similarly there is no requirement in their format specifications to enforce these rules, and most applications consuming the data will interoperate with these naming conventions fine.
Enforcement of lower case/removal of spaces should instead be optional as a user set Parameter.
