ObjectDB Database Search
51-100 of 129 resultsNULL prefered in ORDER BY? Hi! Is there a way to NOT prefer NULL in Order BY? I.e. assume this: @Entity class Hint { private String name; } @Entity class Test { private Hint hint ; } I've got a few Test entries, some do have a hint assigned, some do not (NULL). Now when I | |
EM close causes an exception. We had to change the implemention so that it works also in Linux. Do you need a hint how we solved ... to the original post or a separate issue? Of course, any hint on how to improve ObjectDB will be appreciated ... . If this is the case than it could be a hint for a possible fix. Does it happen only on Linux? Does it happen | |
Pessimistic Lock Timeouts setting. However, there is a standardised query ' hint ' that can be setup to make the underlying DB lock a record for a specific time. The hint property is: "javax.persistence.lock.timeout" I have a situation ... however is lacking in this area (hence why they made it a ' hint ' - that should be considered non-portable | |
Is 2 level cache in use? hint and check if it helps: query.setHint("objectdb.result-fetch", "lazy ... by indexes without accessing the primary data. Currently this hint must be set at the query level (as demonstrated above) - but it should be supported in all other query hint scopes in future | |
how to query by properties of onetomany relations? (Error 990) objects. i adapted my query and it works like expected. thanks for the hint chris Christoph Ernst ... the following query hint : em.setProperty("objectdb.query-language", "JPQL"); The default query language ... to JPQL using a hint the following exception is thrown on attempt to use the new navigation from | |
Problem with @Basic(fetch = FetchType.LAZY) and description properties must have been loaded on the query, ignoring the fetch = FetchType.LAZY hint ... De Clercq LAZY in JPA (unlike EAGER ) is merely a hint , which JPA implementations may ignore ... is still a hint . ObjectDB (as other JPA providers) can only load one-to-one relationships lazily when entity classes are enhanced . support Support | |
a REPLY button will be good!, that can add a hint to which message the author is reply. Sometimes, multiple replies confuse us in tracking the discussing topic, if a hint like this will be good: On 5/13/2011 11:46 AM, James007 wrote at floor 3: line 1 line 2 ... gzdillon Lai Yang If no hint , just a link | |
Need help to analyse very high memory usage by objectdb (PRU, SEV, VAL[]) consumption yet. Can you give us any any hints , which leads to the generation of these objects ... them. Any kind of hints would help us to analyse/fix our problem. We use version 2.6.9_08 in embedded mode. btc_es BTC EmbeddedSystems Small hint @ObjectDB (not related to this thread): I got | |
Listing large number of complicated objects with paging. ( setMaxResults ). Does that number affect? You may try running the query with a lazy fetch hint (as done by ... () objects? I will try lazy fetch hint , but as I understand it will run 50 queries find(Product) while iterating over product list, right? lwalkowski Lukasz Walkowski OK, I just set lazy hint | |
Soft Reference Object Cache Recommendation; I understand that the ObjectDb.conf value I specify ( ) is a HINT to the number of PAGs ... the configuration is indeed a hint . ObjectDB allows up to 80 additional pages (in addition to the pages | |
Catching exceptions from online backup (when it is not an immediate exception)? Maybe a query hint to disable starting the threads ... client-server mode. The query hint to disable automatic starting of the backup thread | |
Memory Leak in EntityManagerFactory ? ours (there might be some additional issues from our side). Could you please give me a hint how we could avoid ... ; or does I miss something ? can you please give me a hint | |
Possible issue with LAZY Loading (unlike EAGER ) is considered in JPA as a hint and in some cases data is fetched eagerly regardless of the hint . This happens, for example, when ObjectDB uses reflection mode (classes are not enhanced | |
Difference performance in ObjectDB Explorer and in java project other useful hints for object db? Performance is better, but still not the same 1000 ms in ... hints . If your classes are not enhanced then try enhancing them. support Support Appreciate your help Konstantin Konstantin | |
Memory error during commit, if @ElementCollection field contains many elements content still requires memory space. Lazy setting in JPA is considered as a hint to the implementation, but the implementation can still load content eagerly. ObjectDB follows the lazy setting hint | |
Failed to write the value of field using reflection (error 363) on LAZY fetch (e.g. a Modell has several Artikels) . When I remove the LAZY hint (query.setHint("objectdb.result ... hints ? The Mapping of class Modell and its member: @Entity class Modell { ... @OneToMany(fetch | |
Mapped (Inverse) LAZY @OneToMany vs. Unmapped LAZY @OneToMany; } } } webel Dr Darren Kelly LAZY in JPA is a hint . If your code is enhanced (as ... .greensoft.objectdb.test.console.TestLazyOneToMany Then ObjectDB follow the hint and the output is: a.listA | |
AnnotationAttrRef jakarta.persistence.Basic.fetch must be eagerly fetched. The LAZY strategy is a hint to the persistence provider runtime. If not specified, defaults to EAGER . Since: JPA 1.0 | |
FieldRef jakarta.persistence.PersistenceConfiguration.QUERY_TIMEOUT JPA Static Field in jakarta.persistence.PersistenceConfiguration QUERY_TIMEOUT Default query timeout hint . Since: JPA 3.2 | |
FieldRef jakarta.persistence.PersistenceConfiguration.LOCK_TIMEOUT JPA Static Field in jakarta.persistence.PersistenceConfiguration LOCK_TIMEOUT Default pessimistic lock timeout hint . Since: JPA 3.2 | |
AnnotationAttrRef jakarta.persistence.QueryHint.name JPA Annotation Attribute in jakarta.persistence.QueryHint String name default null Name of the hint . Since: JPA 1.0 | |
AnnotationAttrRef jakarta.persistence.QueryHint.value JPA Annotation Attribute in jakarta.persistence.QueryHint String value default null Value of the hint . Since: JPA 1.0 | |
AnnotationAttrRef jakarta.persistence.Basic.optional JPA Annotation Attribute in jakarta.persistence.Basic boolean optional default true (Optional) Specifies whether the value of the field or property may be null. This is a hint and is disregarded for primitive types; it may be used in schema generation to infer that the mapped column is not null . If not specified, defaults to true . Since: JPA 1.0 | |
Query.setTimeout(timeout) - JPA Method JPA Method in jakarta.persistence.Query Query setTimeout ( Integer timeout ) Set the query timeout, in milliseconds. This is a hint , and is an alternative to plain jakarta.persistence.query.timeout . Parameters: timeout - the timeout, in milliseconds, or null to indicate no timeout Return: the same query instance Since: JPA 3.2 | |
AnnotationAttrRef jakarta.persistence.ElementCollection.fetch must be eagerly fetched. The LAZY strategy is a hint to the persistence provider runtime. If not specified, defaults to LAZY . Since: JPA 2.0 | |
like operator (String) isn't a problem. The GUI related methods will add implicit a '%' character. Additional hint :  | |
Level 2 cache not hit in @ManyToOne without performance penalty. You can change this behavior by setting the "objectdb.result-fetch" query hint | |
Set timeout for BatchQueryItr ( unknown source ) xirt Sylvain You can set a query execution timeout as a query hint . The many | |
Installing a VM security fix leads to inactive DB. It is really tiresome. As we bought the license years ago there was hinted at a automatic | |
Performance in SELECT statement would be very happy if someone could give me a hint why this query tooks so long. edit: I just tried to remove | |
Performance issue in a query due to compareTo calls Hello, we have a question again regarding query performance. The query: SELECT v FROM Values v WHERE v.step.stepNumber = ? is very slow in comparing to the query: SELECT v FROM Values v WHERE v.stepNumber = ? Can you explain why the first query needs so much time or do you have a hint | |
Change Sequcene Id(...) method is different ( hint to improve efficiency by pre-allocating ids). But you may define a new | |
OutOfMemory in Server came. Can You give some hint , why this OOM happens? jakab Gergely Jakab The memory allocation | |
Web Framework Recommendation for leveraging JPA + ObjectDB + ObjectDB" couple successfully in conjunction with a contemporary Web Framework ? Any hints | |
Entity can be found by find() but not by query it then this could be very helpful in understanding this situation. support Support It seems that the hint | |
Apache Tomee 1.5.2: Failed to use JTA (TransactionManager is not found):126) ... 28 more Any hints please? Thanks a lot in advance. zmirc Mircea Chirac It seems as | |
Problems with Tutorials » JPA Web App (Tomcat) » NetBeans JPA Web App hint as to where the build is failing. Regards, Erick erick.rosas Erick | |
ODB with Netbeans a NetBeans forum. I didn't find these errors in Tools Options Editor Hints Java. However, please notice | |
LAZY @ManyToOne field functions as EAGER (unlike EAGER ) is merely a hint . For example, ObjectDB always loads simple value fields eagerly (e.g | |
combined index not used that is executed using a hint (will be explained in the next post). As you have several heavy queries ... 2 new query hints are introduced in build 2.7.6_01: 1. Selecting a query plan from the sorted list ... ) of the executed query plan (always 1 unless a hint is provided), the total number of query plans in | |
queries under 2.7.6_4 significantly slower than under 2.7.6 hint to request a specific preferred query as discussed in issue #2379 . However, during the work on this issue it was found that the new query plan hint feature that was introduced in 2.7 ... )) [[objectdb.query-plan-text=index(ctso['(TC)'-'(TC)']] The 2nd query requires (using a hint ) to use | |
Best practise loading big data less memory consumption by doing that, too. We would kindly ask you to give us some hints or advice ... then we can do that instead. Thanks for this hint ! Yes, only enhanced classes are used in this example | |
ObjectDB 2.8.0 a query hint ( see issue #2379 ). Added logging when the number of allowed entity classes ... to select a query plan using a query hint ( see issue #2379 ). Fixed a critical bug in index based query | |
Deleting archive log folder causes exception. The only way to get system working is to delete the archive file. Can you provide us some hint | |
Negative snapshot user count exception a link in a private support ticket) we can try getting some hint . support Support On our Dev server | |
ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed Support Thank you very much for your hint . If we enhance all entities then it works. btc_es BTC | |
@FetchGroup in JPA similar to JDO as a hint that this query should return Entities with only those fields filled with data: TypedQuery | |
Tracking changes to new collections (in enhancement mode) after flush A further hint is also that the affected list in the map is still a java.util.ArrayList, not an objectdb | |
Unexpected not reproducable exception during commit, unfortunately we cannot reproduce this issue. Thank you for the hints . best regards BTC btc_es BTC | |
Internal objectdb exception when using different language on a machine.JpaQuery.getResultList(JpaQuery.java:721) btc_es BTC EmbeddedSystems Hello, a hint |