-
The message you sent to iso-power.com/ronnie was rejected because it would
exceed the quota for the mailbox.
The subject of the message follows:
Subject: *SpamL2* Don't pay too much for your drugs. Buy from us.
-
The message you sent to usm59.net/contact was rejected because it would exceed
the quota for the mailbox.
The subject of the message follows:
Subject: THE BIGGEST BUTT!
--
See
http://hudson.qa.jboss.com/hudson/job/hibernate-testsuite-db/./DATABASE=pgsql82,label=UNIX-slim/21/changes
--
[...truncated 6679 lines...]
Finding class java.util.forkOpts
Finding class groovy.lang.forkOpts
Couldn't load Resource groovy/lang/forkOpts.gr
Max Rydahl Andersen wrote:
1. I think it's possible to add a manual collection cache entry update
in the postAction() callback. And it'll probably work.
How would you ensure that the cache is consistent ?
Not a problem. Dirty extra lazy collections are already evicted from the
cache during the
> I propose the following solutions:
>
> 1. I think it's possible to add a manual collection cache entry update
> in the postAction() callback. And it'll probably work.
How would you ensure that the cache is consistent ?
"extra lazy collections" is kinda opposite to what "cached collections" is
