Fix l_quantity data generated by Tpch connector

[pramodsatya]

Resolves prestodb/presto#24010 .

[netlify]

✅ Deploy Preview for meta-velox canceled.

Name	Link
🔨 Latest commit	9953853
🔍 Latest deploy log	https://app.netlify.com/sites/meta-velox/deploys/673355984589ad0008f24ee1

[aditi-pandit]

@pramodsatya : Why is this fix only for l_quantity ? I see that other columns like lineitem.discount are also fixed with decimalToDouble. Do we not see inconsistencies with those columns ?

[pramodsatya]

@pramodsatya : Why is this fix only for l_quantity ? I see that other columns like lineitem.discount are also fixed with decimalToDouble. Do we not see inconsistencies with those columns ?

@aditi-pandit, other double columns like lineitem.discount do not have an inconsistency for SF1 and they need the function decimalToDouble.
For tiny SF, the double column l_extendedprice and identifier columns l_partkey, l_suppkey have a data mismatch, in addition to the Varchar columns containing comments (noted here). Since for all these columns the inconsistency originates from Duckdb's dbgen, I wanted to take it up in a separate PR. Would that be fine?

[aditi-pandit]

Thanks @pramodsatya

[facebook-github-bot]

@amitkdutta has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[amitkdutta]

Thanks @pramodsatya for fixing it so quickly.

[facebook-github-bot]

@amitkdutta merged this pull request in f1ff2df.

[conbench-facebook]

Conbench analyzed the 1 benchmark run on commit f1ff2dff.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details.