Kevin

Ok, closing this issue has it has been addressed.

Hi @AndryHTC, Thanks for reporting this. Current schema and table name validation is quite strict as it is based on this regex: ``` ^((?([a-z_][a-zA-Z0-9_]*|"(""|[^"])+"))\.)?(?([a-z_][a-zA-Z0-9_]*|"(""|[^"])+"))$ ``` As you can see from...

We could relax the validation and just follow Postgres semantics by making unquoted names case insensitive. Note, however, that that would mean that invalid names would make it through to...

Here are 2 candidate regexes to validate table names. The first one is less strict as it allows any character (except quotes) to occur in unquoted names: ```regex ^((?([^"]+|"(""|[^"])+"))\.)?(?([^"]+|"(""|[^"])+"))$ ```...

@KyleAMathews asked for Electric to match the case insensitive behavior of Postgres. There are some corner cases with regard to case insensitivity when using non-latin capital letters: ```SQL CREATE TABLE...

@samwillis yep that's what i meant when i say "case insensitive". It's case insensitive when unquoted and case sensitive when quoted.

@KyleAMathews another surprise when matching ORM behavior is the opposite case: when people create an upper-case table and then query it in lowercase (all unquoted). Note that the original implementation...

@balegas Ok, so i understand we want to be case sensitive and not do any validation ourselves + support quotes for corner cases with schema qualified table names, e.g.: `"foo.bar"."baz"`....