[rules-users] JPA vs Marshaller for session persistence
Mark Proctor
mproctor at codehaus.org
Mon Nov 26 11:55:44 EST 2012
JPA for working memory is indeed an entire snapshot of the working memory per transaction. So you want to avoid a transaction per WM insert/update/delete.
Mark
On 26 Nov 2012, at 09:57, magnusv <magnus.vojbacke at digitalroute.com> wrote:
> Does this mean that the JPA persistence has to write out the entire
> knowledgesession every time a new fact is inserted?
>
> I.e. If I have 279 facts, when I insert fact #280, the JPA will write out
> all 280 facts. It has no way of just writing the delta between 279 and 280?
>
> Thanks
>
>
>
> --
> View this message in context: http://drools.46999.n3.nabble.com/JPA-vs-Marshaller-for-session-persistence-tp4020955p4020964.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
More information about the rules-users
mailing list