Replies: 3 comments 2 replies
-
Both are things we should support, but as far as I know they are not implemented yet. The second issue particularly should be rather simple though. |
Beta Was this translation helpful? Give feedback.
-
Maybe @samansmink can hack the int-returning md5 together quickly? |
Beta Was this translation helpful? Give feedback.
-
Hey lloyd, great that you are enjoying DuckDB!
I have tried this in Postgres, MySQL and SQLite and none of them seem to like this (SQLite and MySQL both truncate the number and return 0, Postgres throws an error). Implementing hexadecimal conversion seems like a good idea to me, but as we strive for good compatibility with other database systems I am curious how you are doing this in the other systems/which functions they have to support this conversion that we are missing? Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hey there.
Some of the other Looker founders and I are working on Malloy, a new experimental data analytics language that eventually translates to SQL. We are looking into DuckDB support (nice job!).
I can't seem to find a way to convert a hexidecimal string into a number. Most other dialects allow hexidecimal literals and casting. For example I would expect.
To return 10.
One of our core features is something called Symmetric Aggregates and the we are currently blocked.
Alternatively, making a version of MD5 that returns a HUGEINT would also work for us.
Any ideas?
thanks,
Beta Was this translation helpful? Give feedback.
All reactions