Those queries are part of a longer analysis process. They are executed only once and each element in the list will occur only once in a query. In this special case creating a temporary table is just an additional step.
My current hack for this problem is to group into n-chunks of 2^16 elements, execute n-queries and just aggregate the result in a vector builder. It does work, it's fast enough (~200ms for 110017 values, overall analysis is running 3h) but it does not feel right :)
Cheers, Steffen
Am 19.02.2013 um 15:58 schrieb Rogach <
platon...@gmail.com>:
> Wouldn't it be better (even wrt performance) to store those values in some sort of temporary table?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups "Slick / ScalaQuery" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
scalaquery+...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>