43 | composite index not used in query used, query plan: Step 1: Process Action (a) instances ------------------------------------ [Step 1a] Scan index com.agile.hummingbird.Action[startDate] locating all the Action (a) instances. [Step 1b] Filter the results of step 1a retaining only results that satisfy: (a.startDate>:1 |
33 | General Performance Issues Illustrated with a Specific Method just by changing the configuration, it is not always that simple. More information is needed ... > </filterPlan> </multiVarPlan> </finalPlans> <sub-planning vars="v$1" filter=""> <step vars="()+v$1 ... (Person[all])" /> </step> <selected-plans> <btreePlan complexity="12.4799" eval="3.70/6.30" variable="v$1 |
32 | Performance issue in a query due to compareTo calls WHERE v.step.stepNumber = ? is very slow in comparing to the query: SELECT v FROM Values v WHERE v ... , cascade = CascadeType.REMOVE) private Values valuesRef; } @Index (members = {"step.stepNumber ... private long stepNumber; @OneToOne (fetch = FetchType.EAGER) private TCStep step |
28 | Slow searching with two indexes the results of step 1 by: desc(any(any(this.id))). [Step 3] Apply selection and prepare final ... == :r order by id desc Query Plan Description ====================== [Step 1] Scan index com ... the results of step 2 by: desc(this.id). [Step 4] Apply selection and prepare final results |
27 | Performance in large transactions PerformanceTest (and test1_OneTransaction and test2_ManyTransactions), mentioned in step 3, are not ... TransactionsPerformance { static int steps = 10000; public static void main(String[] args) { test ... myEntity = new MyEntity(); myEntity = em.merge(myEntity); for (int m = 0; m < steps; m |
24 | Entity can be found by find() but not by query and sometimes we don't get the entity by query. Have you an idea what happens here? btc_es BTC EmbeddedSystems |
10 | Issue with UPPER ? ====================== Step 1: Process Mitglied ($1) instances --------------------------------------- [Step 1a ... ($1) instances. [Step 1b] Evaluate fields in Mitglied ($1) instances. Step 2: Process IndividualProfile ($3) instances (for every result of step 1 |
2 | Report Generation with BIRT and JPA the BIRT report using a chart and a table: The tutorial consists of the following steps: |
2 | Getting Started with JPA and Eclipse boxes and menus might look slightly different but the code would be the same). This tutorial consists of the following steps: |
2 | Getting Started with JPA and NetBeans might look slightly different but the code would be the same). This tutorial consists of the following steps: |
