Dain Sundstrom
Dain Sundstrom
> I didn't think of that. Actually makes a lot of sense! I didn't think of it easier. @martint was complaining about the differences in a chat, and I was...
I'm cool with this
This looks good to me, but if a test is possible, please add that. If not (or really annoying), please let us know, and one of us will merge it...
> should refresh materialized view be a separate permission in the API/SPI It is. [Here](https://github.com/trinodb/trino/blob/master/core/trino-spi/src/main/java/io/trino/spi/security/SystemAccessControl.java#L615) is the check. > should the end user really need permission to the underlying table...
> As another example, the syntax I suggested above makes these two equivalent: > > ``` > SELECT 1 AS x, 2 AS y > ``` > > ``` >...
@wendigo I agree the changing of case really sucks, but it is a existing issue.
Updated to the `{}` syntax
> See [#23795 (comment)](https://github.com/trinodb/trino/issues/23795#issuecomment-2423326758) @martint that sounds great. It means that we have no concern that something useful will be used for this. I don't see us ever implementing that...
> The current behavior with literals is ambiguous to me. For instance, I expected the following statement returns timestamp type at a glance, but it returns varchar type. > >...
I expect people won't mix the syntax, and instead would do this: ``` '2007-08-09 9:10:11 Europe/Berlin'::TIMESTAMP ``` So the original expression would be: ``` '2007-08-09 9:10:11 Europe/Berlin'::TIMESTAMP::VARCHAR ```