the error message should be `cannot use keyword "user" here` when use one of the keywords as a column alias about duckdb HOT 3 CLOSED

Thanks for opening this issue! Based on our automated check, it seems that your post contains some code but it does not use code blocks to format it.

Please double-check your post and revise it if necessary. To employ syntax highlighting, it's recommended to use code blocks with triple backticks, e.g.:

```sql
SELECT ...
```

If this is a false positive, feel free to disregard this comment.

from duckdb.

Hi @l1t1,

Two things:

1. Please read the instructions by the @duckdblabs-bot in the previous comment and apply them to your post.

2. Can you please provide an explanation on what your use case for DuckDB is? Your recent issues present corner cases that are extremely rare and have little to no practical impact on DuckDB's users. For example, using more than a few UNION ALL clauses is very rare as there are many other ways to insert multiple rows into database, which renders #10452 irrelevant. Is your goal to find bugs in DuckDB a part of an assignment (e.g., a thesis work)?

Thanks,
Gabor
Developer relations @ DuckDB

from duckdb.

Thanks for the report! This is not a bug as user is a keyword. Better error messages in the parser would be great but that would require a parser rewrite/move away from yacc/bison which is not happening in the short to medium term.

from duckdb.