does presto have any plan about support implicit conversion (from number to varchar )

[trinodb]

does presto have any plan about support implicit conversion (from number to varchar )

[martint]

Adding implicit casts between numbers and strings can be problematic because it may introduce ambiguities when resolving which functions and operators to call.

It also introduces usability problems. Take a look at these examples:

1 == '1' is true but 2.0 == '2' is false
9 < 10 is true but 9 < '10' or '9' < 10 is false

In the future, we plan to allow users to define implicit casts via plugins, but that's a longer term feature. We don't expect to have this feature built into the core, though, for all the reasons above and the fact that it's not standard SQL behavior.

It take huge cost changes for rewrite Hive scripts

Perhaps, what would be valuable is for someone to build a tool to translate between Hive queries and Presto queries.

[sopel39]

I don't think implicit number -> string cast is part of SQL standard:

A number is assignable only to sites of numeric type.
If an assignment of some number would result in a loss of its most significant digit, an exception condition is raised.
If least significant digits are lost, implementation- defined rounding or truncating occurs, with no exception condition being raised.
The rules for arithmetic are specified in Subclause 6.26, “<numeric value expression>”.

Maybe we could have a compatibility toggle for such feature? @martint ?

[hereTac]

Ye. Good idea. It is good for both.

[aniruddha-pe]

Hey, is this being taken up anytime soon ? If not as a default, probably can be provided as an option to user to set true before running a query like hive.groupby.orderby.position.alias=true