Barry Pollard

> There's probably no way to leave the data_type_identifier if the identifier is something, right? Sorry don't get what you mean?

Only way to do that at present would be to inline ignore. ```sql SELECT * FROM normal.table1 INNER JOIN Weird.Table2 -- noqa: L014 WHERE ....etc. ``` Or enhance the rule...

Because you want to ignore the word, if it's preceded by the ignore words. So probably what you want is to check the parent with this: ```py parent: Optional[BaseSegment] =...

I'm also curious as to how you got the exception. Would like to solve that too but can't recreate it.

> @tunetheweb, @fdw: Should we update the title of this issue? It seems to have changed from a bug to an enhancement request. Or both? Changed to what I understand...

I'd really like to solve the crash too. Here's what I'm doing: Setting my `.sqlfluff` file to this: ``` [sqlfluff] dialect = tsql [sqlfluff:rules:L014] # Unquoted identifiers extended_capitalisation_policy = pascal...

While this seems sensible, are we sure it’s an issue? Or is SQLFluff perhaps efficient enough to stop after the mismatching the first keyword (that this optimisation implies) so checking...

This this require fixing #3345 ? Or could we fix this at the same time?

No, because of nesting. What’s to stop that closing the match from below after the first `END` and producing an unparsable result because of this? ``` BEGIN BEGIN ... END...

At the moment `StartsWith` With terminator or `GreedyUntil` terminates on first match. I want a new `Balanced` type that is like `GreedyUntil` but won’t allow early closing. As I say...