Barry Pollard

"Incorrect" is a bit strong IMHO, and uptake of KiB is still not great in general. I think [this answer](https://ux.stackexchange.com/a/13850) still stands to be honest - 7 years later! A...

@OTooleMichael was this fixed with #2884 ?

Should this: ``` [sqlfluff:templater:jinja:macros] full_name = {% macro full_name(fn_ref) %}{{fn_ref}}{% endmacro %} ``` Actually be this?: ``` [sqlfluff:templater:jinja:macros] expand_udf_name = {% macro expand_udf_name(fn_ref) %}{{fn_ref}}{% endmacro %} ``` I get templating...

Here's the expanded sql: ```sql SELECT *, `exampleUDF`(ColumnName1).* REPLACE ( COALESCE( `exampleUDF`(ColumnName1).Element, NULL ) AS Element ) FROM exampleDataset ``` To be honest I don't understand this SQL. Are you...

Yeah personally I think inheriting from multiple dialects (unless there is a clear inheritance like ANSI -> Postgres -> Redshift) is a bit confusing and difficult to maintain. However, the...

To @colinbendell 's point in #181, instead of adding `finalXXX` timings, we could add the following: - `interimResponseStart` (between `secureConnectionStart` and `responseStart`) and change `responseStart` to mean final response start,...

> We don't always need equivalent opposites, like with `secureConnectionStart`. I think that's OK Yeah I know, but there we don't have `secureConnectionEnd` at all (though nothing to stop it...

> > We don't always need equivalent opposites, like with `secureConnectionStart`. I think that's OK > > Yeah I know, but there we don't have `secureConnectionEnd` at all (though nothing...

> Please don't prefix anything with early. If we want to support interim HTTP responses, call it that. Expect the HTTP to define more 1xx codes, because its been a...

> Perhaps earlyHintsStart ? I'm against being that specific. Who knows what the future will bring.