Something on dynamic filtering

[d6y]

User suggestion: http://underscore.io/blog/posts/2015/05/06/essential-slick.html#comment-2111361019

[jonoabroad]

Should this be in Chapter 5 or Chapter 2?

Either way, I'm having a look.

[d6y]

Oh yeah, it could be chapter 2 if we've introduced enough of how Queries work. I suspect it can be written and then decide where it goes :-)

If you're on this and getting progress on it, cool.

If not...

I'd forgotten about this. I'm tempted to say put it in the Icebox milestone for another time. But a user did ask for it, and it is something that came up at REDACTED too.

Perhaps we should think about "case studies", which is a concept that Essential Scala has for more application focused bits of code.

[jonoabroad]

Moved to ice box after discussion with Richard.

[d6y]

Related, dynamic sorting: http://stackoverflow.com/questions/42383842/dynamic-order-by-in-scala-slick-with-several-columns

via message on Slick mailing list from Antonio reKiem:

According to the slick documentation in this part:

Be aware that a single ORDER BY with multiple columns is not equivalent to multiple .sortBy calls but to a single .sortBy call passing a tuple

But what happend if i want to make a dynamic order by (variable number of colums)? , since i can not create dynamic sized tuples. I already asked this in stack overflow, but using the answer that I received, I am still generating chaining calls to sortBy. The query is created fine, but then why the documentation says is not equivalent?

[d6y]

See also: https://stackoverflow.com/questions/49838709/slick-pass-in-column-to-update/49873298#49873298

[Daenyth]

FWIW https://gist.github.com/Daenyth/75df5633b0649b94a98a99bbe35dd45c

[d6y]

Relates to: #163