davlee1972 commented on PR #1738:
URL: https://github.com/apache/arrow-adbc/pull/1738#issuecomment-2072885856

   I'm not asking you to be a SQL dialect, but you might want to incorporate 
the dialects into the CI builds so they find the right table name..
   
   Here's some samples..
   
   ```
   from sqlglot import exp
   from sqlglot.optimizer import optimize
   
   table_names = {
       'lower_case | unquoted': exp.table_("dummy", quoted=False),
       'lower_case | quoted': exp.table_("dummy", quoted=True),
       'upper_case | unquoted': exp.table_("DUMMY", quoted=False),
       'upper_case | quoted': exp.table_("DUMMY", quoted=True),
       'mixed_case | unquoted': exp.table_("duMMy", quoted=False),
       'mixed_case | quoted': exp.table_("duMMy", quoted=True)
   }
   
   dialects = ['snowflake', 'postgres', 'mysql', 'tsql', 'oracle']
   
   for dialect in dialects:
       for k, v in table_names.items():
           print("dialect: " + dialect + ", case + quoted: " + k)
           print("in: " + str(v.this))
           print("out: " + optimize(v, dialect=dialect).sql())
           print("")
   ```
   
   Dialect results..
   
   ```
   dialect: snowflake, case + quoted: lower_case | unquoted
   in: dummy
   out: "DUMMY"
   
   dialect: snowflake, case + quoted: lower_case | quoted
   in: "dummy"
   out: "dummy"
   
   dialect: snowflake, case + quoted: upper_case | unquoted
   in: DUMMY
   out: "DUMMY"
   
   dialect: snowflake, case + quoted: upper_case | quoted
   in: "DUMMY"
   out: "DUMMY"
   
   dialect: snowflake, case + quoted: mixed_case | unquoted
   in: duMMy
   out: "DUMMY"
   
   dialect: snowflake, case + quoted: mixed_case | quoted
   in: "duMMy"
   out: "duMMy"
   
   dialect: postgres, case + quoted: lower_case | unquoted
   in: dummy
   out: "dummy"
   
   dialect: postgres, case + quoted: lower_case | quoted
   in: "dummy"
   out: "dummy"
   
   dialect: postgres, case + quoted: upper_case | unquoted
   in: DUMMY
   out: "dummy"
   
   dialect: postgres, case + quoted: upper_case | quoted
   in: "DUMMY"
   out: "DUMMY"
   
   dialect: postgres, case + quoted: mixed_case | unquoted
   in: duMMy
   out: "dummy"
   
   dialect: postgres, case + quoted: mixed_case | quoted
   in: "duMMy"
   out: "duMMy"
   
   dialect: mysql, case + quoted: lower_case | unquoted
   in: dummy
   out: "dummy"
   
   dialect: mysql, case + quoted: lower_case | quoted
   in: "dummy"
   out: "dummy"
   
   dialect: mysql, case + quoted: upper_case | unquoted
   in: DUMMY
   out: "DUMMY"
   
   dialect: mysql, case + quoted: upper_case | quoted
   in: "DUMMY"
   out: "DUMMY"
   
   dialect: mysql, case + quoted: mixed_case | unquoted
   in: duMMy
   out: "duMMy"
   
   dialect: mysql, case + quoted: mixed_case | quoted
   in: "duMMy"
   out: "duMMy"
   
   dialect: tsql, case + quoted: lower_case | unquoted
   in: dummy
   out: "dummy"
   
   dialect: tsql, case + quoted: lower_case | quoted
   in: "dummy"
   out: "dummy"
   
   dialect: tsql, case + quoted: upper_case | unquoted
   in: DUMMY
   out: "dummy"
   
   dialect: tsql, case + quoted: upper_case | quoted
   in: "DUMMY"
   out: "dummy"
   
   dialect: tsql, case + quoted: mixed_case | unquoted
   in: duMMy
   out: "dummy"
   
   dialect: tsql, case + quoted: mixed_case | quoted
   in: "duMMy"
   out: "dummy"
   
   dialect: oracle, case + quoted: lower_case | unquoted
   in: dummy
   out: "DUMMY"
   
   dialect: oracle, case + quoted: lower_case | quoted
   in: "dummy"
   out: "dummy"
   
   dialect: oracle, case + quoted: upper_case | unquoted
   in: DUMMY
   out: "DUMMY"
   
   dialect: oracle, case + quoted: upper_case | quoted
   in: "DUMMY"
   out: "DUMMY"
   
   dialect: oracle, case + quoted: mixed_case | unquoted
   in: duMMy
   out: "DUMMY"
   
   dialect: oracle, case + quoted: mixed_case | quoted
   in: "duMMy"
   out: "duMMy"
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to