[Feature Request] Expose generic unary, binary and ternary operators

[hstanford]

It would be useful to allow syntax similar to

var query = user.select(user.id).where(user.name.binary('<@>', 'example'));

('<@>' is a placeholder operator, focus is the 'binary' node)
The interface of each function could be:

...unary(operator)
...binary(operator, val)
...ternary(operator, separator, middle, right) 

Or perhaps a single 'operation' method that would decide whether to use a unary, binary or ternary node depending on the number of arguments:

...operation(operator, ...)

This would be useful for implementing currently unsupported operators like '<->' in postgres (new in 9.6) or even user-defined operators.
Would you be happy to support this? I am happy to submit a pull request.

[brianc]

I like that idea!

…

On Sat, Aug 5, 2017 at 4:56 AM, hstanford ***@***.***> wrote: It would be useful to allow syntax similar to var query = user.select(user.id).where(user.name.binary('<@>', 'example')); ('<@>' is a placeholder operator, focus is the 'binary' node) The interface of each function could be: ...unary(operator) ...binary(operator, val) ...ternary(operator, separator, middle, right) Or perhaps a single 'operation' method that would decide whether to use a unary, binary or ternary node depending on the number of arguments: ...operation(operator, ...) This would be useful for implementing currently unsupported operators like '<->' in postgres (new in 9.6) or even user-defined operators. Would you be happy to support this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#369>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADDoddpVfe9O6R4NjXdPGL55Obe3Ujcks5sVDxjgaJpZM4Oua3J> .

[hstanford]

Thanks! Pull request submitted #370

[seokgyo]

This looks very cool? Is there any updates?