we are using this query select a from Action a where (a.state = 2 or a.state = 3) and a.type = 0 and a.transferred = 0 and see a very strange query plan, an index scan for an entry that is not used at all in the query, and according to that plan there is no result: Query plan 1/2 description ============================ [Step 1] Scan index com.agile.hummingbird.Action[endDate] locating all the Action (a) instances. [Step 2] Retrieve fields in Action (a) instances. [Step 3] Filter the results of step 2 retaining only results that satisfy: (a.transferred=0). [Step 4] Filter the results of step 3 retaining only results that satisfy: (a.type=0). [Step 5] Filter the results of step 4 retaining only results that satisfy: or((a.state=3),(a.state=2)). [Step 6] Apply selection and prepare final results.
no query result
#1
#2
On the 20GB database with version 2.8.9_06 there are 1421 results in the Explorer for:
select a from Action a where (a.state = 2 or a.state = 3) and a.type = 0 and a.transferred = 0
ObjectDB Support
#3
Query plan 1/2 description ============================ [Step 1] Scan index com.agile.hummingbird.Action[state, subType, type, startDate, endDate, detail, transferred] locating Action (a) instances that satisfy: and(and(or((a.state=3),(a.state=2)),(a.type=0)),(a.transferred=0)). [Step 2] Apply selection and prepare final results. <btreePlan 15.757 4.74/5.29 a(Action) index(-161:sstsedt[and(and(or([3->3:notNull],(a.state=2)),[pos<2>0->0:notNull]),[pos<6>0->0:notNull])]) />
ObjectDB Support
#4
we see now that this index is not active Scan index com.agile.hummingbird.Action[state, subType, type, startDate, endDate, detail, transferred] Even we have in the db configuration the entry to automatically create/adjust indexes we have the message in the log: index sstsedt cleared then it reports reports about the batches and finally the completion but still it is inactive by the way, we do not have any toolbars ... here for editing (using Safari)
#5
+ edit of a already save post does not work, too
#6
Regarding the issues with the forum, could you please refresh the browser? We had a problem with JS compression that was too aggressive, but now it seems that these issues are solved.
About the inactive index, it is unclear why it is inactive. It should become active again after the index is rebuilt so this should be investigated further. If you want to send a database with demonstration of all today's issues we can look at it.
ObjectDB Support
#7
it works again, thanks.
regarding the issue, sorry our fault the explorer was started during the reindexing and the inactive was not refreshed. Issue solved