Moritz Onken (o...@houseofdesign.de)

Hi, especially mst,

we talked about rewriting _collapse_result to allow multiple has_many
joins on the same level.
I added some code to it, which basically removes any duplicates.
I know we talked about that on IRC and you told me that this is dirty
hack. As of that the code is only run if you set distinct => 1.
If set so the results are exactly what you would expect, no duplicates!

Please have a look and tell me if this is working for you or if we
should try something else.

Attachment: 77collapseresult.t

Attachment: unnamed_plain_text.txt

Attachment: resultset.diff

Attachment: unnamed_plain_text.2.txt

After talking to mst, the exception was degraded to a warn.
Patch attached.

greets,

moritz

Attachment: resultset.diff

Attachment: test.diff

Actually you need to set that parameter somewhere else.
See the docs to Session::Store::FastMmap fore more information.

>
>   Authentication
>                 Session
>    Session::Store::FastMmap
>    Session::State::Cookie

Storing the session with FastMmap is not a good idea. If the cache_size
of FastMmap is exhausted it starts dropping sessions to make space
for new sessions.

You can change the cache size by setting it like this (default is 5mb):

cache:
     backend:
         class: Cache::FastMmap
         cache_size: 100m

But I'd suggest you change to Session::Store::DBIC or something else
which does not drop sessions if you run out of space.

greets,

moritz

It's Content-type => ...