Jake Wheat

There is a straightforward alternative which I think is standard, and you can use any expression in it: ``` select cast('1 hour' as interval); ```

Here's a little follow up on this syntax. I think Postgres's interval syntax is (mostly) standard. This interval syntax in ANSI can only be used to create literals, it is...

Thanks for the report, I would be happy to merge a pull request

I think this is the solution: https://github.com/JakeWheat/simple-sql-parser/issues/8 This has a whitelist which overrides the blacklist on specific names in the App parser only. If this is needed for other bits...

Regarding `CAST(blah AS DATE)`, `date '2001-01-01'`, or `'2001-01-01'::DATE`, in case there is ambiguity, I think these should parse to a cast, to a special syntax (this is a literal only,...

I'm still not sure if removing these from the keyword list so that they parse, or adding them to the function whitelist so they only parse as Apps and not...

Thanks for the report. Can you try to parse the statement which is on line 305 on its own and see if that gives the same error, and if so,...

The following similar code works: ```parseStatements postgres "" Nothing "INSERT INTO tbl (col) VALUES(e'a\\'sd')"``` So almost all the code needed is there, it just needs a bit of tweaking. I...

Thanks for the report, I would be happy to merge a pull request. I didn't check the code, but it shouldn't even restrict the type name in a cast expression...

I think it should support this, can you give a complete example of something that fails?