Jake Wheat
Jake Wheat
Looks nice! Is there anything to follow up with on this issue?
Supporting this has never been considered, it's just an oversight. I think the right approach is a whitelist like with the function names. Usually, removing things like this from the...
You can now override these keyword lists in 0.6.0, in this case you could add 'CURRENT_TIMESTAMP' to the list of identifier keywords in the dialect. I hope to get round...
Transforming SQL and maintaining the formatting of the unchanged bits (and preserving comments) is something I've wished I've had on many occasions, so I think this would be a great...
It's on my list, but I don't know when I'll get round to it. It seems there are no renames in ansi sql. It's a very basic and necessary feature...
Hi Steve, The system doesn't support this syntax, and there are no plans to support it on my side, but a patch would be welcome!
I have a tutorial on implementing SQL parsing in Haskell! http://jakewheat.github.io/intro_to_parsing/ > Is there a way of getting the parser (parseStatements) to ignore unsupported statements This is an interesting idea...
I think this might be the intended behaviour. What syntax do you expect to `select *, t.*, count(*)` to parse to? What syntax do you think it _should_ parse to?...
Here is the reason why it parses that way. When you parse e.g. ``` create table a.b ( ... ``` You can easily parse the `a.b` as a `[Name]` or...
Does it work if you use the postgresDialect in the parse flags? The default dialect is ANSI which doesn't support this syntax for casts. The dialect support is a bit...