Hi,
I have a LEFT JOIN, which looks like this:
|
| entityManager.createQuery("SELECT t FROM Template t LEFT JOIN t.messages c WHERE t.client.hostname=:ch GROUP BY t.id, t.subject, t.text, t.client ORDER BY count(c)").setParameter("ch", client.getHostname()).getResultList();
|
The problem is that the larger the table grow the poorer the performance is. After a while it takes about 3-4 seconds to execute.
Any ideas how I could optimize this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045006#4045006
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045006
"tom.baeyens(a)jboss.com" wrote : you can update process definitions. (you have to evict the process definitions in hibernate's second level cache, though)
|
| it is not encouraged, just as modifying java byte code in a running program is not encouraged. you can get into trouble real easy.
|
| same goes for migrating process instances to a newer version. we plan to provide some support for it in the future, but it is easy to end up trouble.
|
| regards, tom.
could someone please explain this a little more or give me a link to this .
I'm using jbpm 2. is this posibble here ?
Also is there a tutorial for migrating from jbpm 2 to jbpm 3.
I see the archive migration, but what happens to my existing process instances in DB ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044997#4044997
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4044997