It's because this kata is using postgresql, and has sqlite disabled. I'd rather this kata be categorized as PostgreSQL then, to be honest, this threw me off too.

I thought BigInteger was disabled for this one

https://www.postgresql.org/docs/15/functions-string.html, you can also use the site's search functionality.

ok....

Guys where should i go to find all these function names such as to_hax() and translate() ?
Is there a comprehensive list of them?

I apologize for missing it and thank you for changing the status of my previous comment.

Please use spoiler flag next time.

you do not capitalize the first character

Why did you change the table name to d (assuming this is in fact what you did)? And why is this best practices?

I was pondering about that too, allbudzeet20. Looks like VARBINARY is part of the SQL 2016 standard, but currently not supported by postgresql: https://www.postgresql.org/docs/current/unsupported-features-sql-standard.html (although it does indeed support to_hex).

thanks for showing me how this is done. Can someone answer why all these solutions I search for don't work? like one site said you convert to hex like CONVERT(varbinary(8), column), but when I tried that it didn't even recognize varbinary, but on the site it said oh this will definitely return a hex value - what am I doing wrong? Seems like most of the ways of doing things I search for don't work/the interpreter or w/e on this site doesn't recognize them.

This kata shouldn't be 5kyu for c#, but we can't blame you for using the tools of c# if they're not forbidden. I rate this solution as best practice, but not clever.

Omg RLY?
I think its not what about kata was..........................