6 | Mapped By Fetch is very Slow in my application is more due to that problem than the left join one. ( Note : The left join index ... . Setting an index on the owner side of the relationship (MyEntityChild.myEntity) may improve |
6 | odb files and config file file '/db/account.odb' viewId=/index.xhtml location=/Users/USER/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/PROJECT/index.xhtml phaseId=RENDER_RESPONSE(6) And I read |
6 | Rename Application StringIdentity datastore and just change its "id" attribute? (And update indexes and references appropriately?) Or ... the primary key (id) of objects, since that may affect references from other objects and indexes. support Support |
6 | Failing to read entities under load in multithreaded tests() { return version; } } @Entity @Indices({ @Index(members={"oidId", "type"}), @Index(members={"parentAcl"}) }) public class TestEntity extends TestIdHolder { private static |
6 | Query performance in general. Would it make sense to have indexed fields first and then the others, or ... and date where id is indexed and date is not. Would it make sense to have "WHERE $1.id > ... AND $1.date |
6 | Performance tuning, best practices="2048mb" max-threads="48" /> <index-update enabled="true" priority="40" /> <query-cache results="1024mb ... to improve performance is to explore that query, rephrase it if possible and/or define additional indexes. support Support |
1 | Unexpected Exception (Error 990) with ArrayIndexOutOfBoundsException.ArrayIndexOutOfBoundsException: Index 5 out of bounds for length 0 java.lang.ArrayIndexOutOfBoundsException: Index 5 out of bounds for length 0 at com.objectdb.o.UTY.L(UTY.java:1440) at com.objectdb.o.ENH |
1 | Query execution causes an unexpected internal exception (Error 990) an unexpected index state during a query update. You should see some log lines starting at "Attempt to remove a non existing index entry" in the ObjectDB server log file. Could you please post |
1 | ObjectDB 2.8.0 #2412). Added logging to diagnose unexpected duplicate index entry (issue #2403). Fixed a bad ... hint (see issue #2379). Fixed a critical bug in index based query execution (issue #2414). Fixed a bug |
1 | Logical "or" works not correcly when field is @Id and first position later it seems, whenever an indexed field (means b-tree can used) is inside an or condition ... ':notNull])]) /> This means, everybody using or conditions for indexed fields went into wrong results |
