Dietr1ch commented on issue #13649:
URL: https://github.com/apache/datafusion/issues/13649#issuecomment-2585573102
> I agree it is confusing, but if we switched the default value to `false`
then other users would be confused.
I doubt it'll be as confusing since the error they would get even today
wouldn't seem wrong.
Consider the two scenarios,
- Today, with identifier normalisation, I query for say `select UserId`, and
get an error saying that the `user_id` column wasn't found, but I didn't type
that, which is perplexing. I then proceed to look at my data and find that I
did type `UserId` correctly.
Now I know I'm typing the right thing and it doesn't work. Maybe I notice
the snake_casing, but I have no idea how to avoid it as whatever I type gets
modified. Using quotes to avoid normalisation is not the first thing that may
come to mind.
- Debugging isn't easy
- Figuring out what to do is hard, or at least annoying
- Quote if you know SQL pitfalls.
- Rename your columns.
- Cry
- If the identifier normalisation was off by default, the errors would be
alright.
I'd keep my typing `UserId` to query the `user_id` column like I used to do,
but after an update this new error appears. "Couldn't find column `UserId`", so
I check my data and see that in fact the column was called `user_id`. I fix
that in my query and it works.
- Straightforward debugging
- My input isn't being changed arbitrarily, so the obvious solution of
fixing the typo works.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
