You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Datafusion] Datafusion queries involving a column name that begins with a number produces unexpected results #108
Activity
alamb commentedon Apr 26, 2021
Comment from Ben Sully(sd2k) @ 2020-11-08T11:46:18.008+0000:
This behaviour seems consistent with Postgres at least: {{❯ psql}} {{psql (12.4)}} {{Type "help" for help.}} {{ben=# create table foo ("16_20mph" integer, "21_25mph" integer);}} {{CREATE TABLE}} {{ben=# insert into foo values (1, 2), (3, 4);}} {{INSERT 0 2}} {{ben=# SELECT 16_20mph, 21_25mph FROM foo;}} {{ _20mph | _25mph }} {{--------+--------}} {{ 16 | 21}} {{ 16 | 21}} {{(2 rows)}} {{ben=# SELECT "16_20mph", "21_25mph" FROM foo;}} {{ 16_20mph | 21_25mph }} {{----------+----------}} {{ 1 | 2}} {{ 3 | 4}} {{(2 rows)}}Jefffrey commentedon Jan 7, 2023
I believe this can be closed as its expected behaviour stemming from sqlparser, recent relevant discussion: apache/datafusion-sqlparser-rs#768 (comment)
alamb commentedon Jan 8, 2023
I agree -- thanks @Jefffrey -- I agree this is "expected behavior" in the sense that it is what postgres does even though it is not very obvious
build: Add tpcds-sf-1 to license header excluded list (apache#108)