Shane

Depends on [upstream PR](https://github.com/tomjaguarpaw/haskell-opaleye/pull/552). The question I have there applies here to — what should we call `orderBy` given that the name "`orderBy`" is already taken?

@ocharles suggested just calling it `orderPartitionBy` which I've done. I've added documentation now too so it's just the upstream PR that this is waiting on.

I saw a thing recently that suggested using `&` instead of backticks to achieve the same effect, i.e., `"foobar" & ilike "%oo%"`. Not sure if I'd ever write code like...

This probably isn't something we're going to get around to any time soon, but in the mean time you can do this: ```haskell ( Expr [a] -> Expr [a] ->...

I appreciate all the input from @tstat and and @mitchellwrosen here. I still don't have a good intuition for this but hopefully that will come! Having said that, I don't...

I think this is actually possible in Opaleye, we need to use the [`RepExpr`](https://hackage.haskell.org/package/opaleye-0.7.2.0/docs/Opaleye-Internal-PrimQuery.html#t:PrimQuery-39-) constructor of `PrimQuery`.

For what it's worth @intractable, here's a snippet from CircuitHub's codebase that provides a function `elem :: Sql DBEq a => Expr a -> Expr [a] -> Expr Bool` which...

Ah, I didn't even know Postgres had named parameters. I think the bigger issue here though is going to be that `tc.admin_log_in` seems to itself return a query? I don't...

This is completely untested right now, but I'm interested to see if either of you have any comments on the work so far before I go any further with it.

This is based on the refactoring in #575.