I'm guessing you can't use `(x: number, y: string) => x === parseInt(y)`?
If you are only reading from a table I don't think any relational database implementing MVCC would lock anything.
Functions don't have to be optimization barries. If you mark them as stable or immutable I believe postgres will inline them whenever they are used such that they can be optimized.
I'm guessing you can't use `(x: number, y: string) => x === parseInt(y)`?
If you are only reading from a table I don't think any relational database implementing MVCC would lock anything.
Functions don't have to be optimization barries. If you mark them as stable or immutable I believe postgres will inline them whenever they are used such that they can be optimized.