15 | 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 the access ... 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 |
13 | 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 ... this area (hence why they made it a 'hint' - that should be considered non-portable). Thanks |
13 | Is 2 level cache in use? and by navigation (and not in queries). You may try the following undocumented ObjectDB query hint ... 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 versions |
13 | how to query by properties of onetomany relations? (Error 990) for the hint chris Christoph Ernst Support of direct navigation from collections (with no JOIN ... using standard JPQL by setting the following query hint: em.setProperty("objectdb.query-language ... extensions. When the query language is set to JPQL using a hint the following exception is thrown |
11 | Problem with @Basic(fetch = FetchType.LAZY) = FetchType.LAZY hint. Am I doing something wrong? (I am using objectdb-2.3.6_10) tia, Wim wim DC Wim De Clercq LAZY in JPA (unlike EAGER) is merely a hint, which JPA implementations may ignore. ObjectDB ... is still a hint. ObjectDB (as other JPA providers) can only load one-to-one relationships lazily when entity classes are enhanced. support Support |
11 | Iterating over large result set can use cursors. With some JDBC drivers there is a hint, that driver should fetch data in packages ... with one query by running the query with a hint "objectdb.result-fetch" set to "LAZY". Another option is to use ... with one query by running the query with a hint "objectdb.result-fetch" set to "LAZY". That was first thing I |
4 | OneToOne.fetch is a hint to the persistence provider runtime. Default value: javax.persistence.FetchType.EAGER Since: JPA 1.0 |
4 | javax.persistence.OneToOne runtime that the associated entity must be eagerly fetched. The LAZY strategy is a hint to the persistence |
4 | javax.persistence.ManyToMany fetched. The LAZY strategy is a hint to the persistence provider runtime. Default value: javax |
2 | Best practise loading big data that, too. We would kindly ask you to give us some hints or advice how to access the data or how to configure the DB ... then we can do that instead. Thanks for this hint! Yes, only enhanced classes are used in this example ... for that. Your hint regarding the iterator is very helpful to understand how the entities are referenced. I |
