Plan to add a new flavor: Presto SQL

[doyonghoon]

I am not sure if it would be an excessive demand, but I found that it will be a sole-choice for me to use in my project if Presto SQL is supported. Thanks!

[huandu]

From my observation, Presto SQL is the same as MySQL SQL syntax except following. Correct me if I'm wrong.

• Presto uses LIMIT n OFFSET m whereas MySQL uses LIMIT n, m;
• Presto uses from_hex('abcdef') to create binary data whereas MySQL uses 0xabcdef to do so.

I can implement new Presto flavor in this weekend if above is all I need to do.

[doyonghoon]

@huandu Hey, thanks for the quick response! Yeah, that looks good to me. In a case where missing pieces are found, then I may be available to open a new PR to cover other corner cases. Greatly appreciated your time!

[tengteng22]

From my observation, Presto SQL is the same as MySQL SQL syntax except following. Correct me if I'm wrong.

• Presto uses LIMIT n OFFSET m whereas MySQL uses LIMIT n, m;
• Presto uses from_hex('abcdef') to create binary data whereas MySQL uses 0xabcdef to do so.

I can implement new Presto flavor in this weekend if above is all I need to do.

From prestoDB doc I think OFFSET goes before LIMIT.
This caused issue when I use this library to build a SQL query against AWS Athena (which is Presto SQL):
mismatched input 'OFFSET'. Expecting: <EOF>