Oliver Borchert
Oliver Borchert
My solution was to move to https://github.com/fullstorydev/grpcui 🙃
Removing pooler-specific annotations is a hacky solution imo. The reason for these annotations is to allow external operators to reload the pooler Pods once the TLS secret changes. When using...
Yes, that sounds reasonable. So can I update the PR with pooler specific annotations in the operator config?
Hey @bchrobot I don't currently need the functionality anymore, so I'm unlikely to work on it soon ... feel free to take over!
@fmms where would these function names be added? `RESERVED_KEYWORDS` or `UNRESERVED_KEYWORDS` or somewhere completely else? And would I need to add them somewhere else (e.g. to allow expressions to contain...
Mh or just updating `bare_functions` as you pointed out above ... 😅
@fmms can you verify whether the PR satisfies your needs?
How does your `.sqlfluff` file look like, @fmms? Using the following, ``` [sqlfluff] dialect = tsql ``` it correctly formats your example query for me -- even with the current...
That's strange, I get a different result ... can you also set the following config option: ``` [sqlfluff:rules:L030] extended_capitalisation_policy = upper ```
I see... in that case, I observe the same issue as you do, L010 does not pick up these keywords. @tunetheweb any idea why that is the case?