About named queries

issue

JPA Metamodel (JPA 2.0)

The JPA Metamodel API enables examining the classes, fields and properties of the persistent object model, similarly to the Java reflection API. The JPA Metamodel API has a major role in defining queries using the JPA Criteria API.... The JPA Metamodel API has a major role in defining queries using the JPA Criteria API. ObjectDB Support ...

 
forum_thread

explorer feature request: ability to auto refresh

Request for feature: Ability to auto-refresh an explorer view, say at regular intervals of a few seconds. (at a minimum one ought to be able to manually refresh, for example the list of persistent types). additionally, it would be useful to be able to view an embedded database (read only mode) via the explorer.   #1 2011-04-27 07:22 Request for feature: Ability to auto-refresh an explorer view, say at regular intervals of a few seconds. ...

 
forum_thread

Partial Indexing

I have a question about partial indexing. For example, a field of String type ttt, will be distinguished by the first 5 characters, then I can make a index of substr(ttt,1,5) in MySQL. With ObjectDB, how can I write the annotation for this purpose? TIA Institute of Computer Technologies ... @PreUpdate) . The new field should be indexed and used in queries. ObjectDB Support ObjectDB - Fast Object ...

 
forum_thread

persists and update together ?

hello on mysql i've seen;   INSERT INTO table (a,b,c) VALUES (1,2,3),(4,5,6) ON DUPLICATE KEY UPDATE c=VALUES(a)+VALUES(b);   This query , inserts data or updates if its already available and this will reduce finding same object again. On jpa : User obj2 = ...; #1 2012-07-17 15:03 hello on mysql i've seen;   INSERT INTO TABLE ( a , b , c ) ...

 
forum_thread

impossible to drop a table with 50 million objects

when trying to execute in explorer (max heap size 1GByte) delete from LogEntry l it comes up with a Java heap error after 20 minutes of executing. How to empty such a table ?     #1 2017-06-28 05:49 when trying to execute in explorer (max heap size 1GByte) delete from LogEntry l it comes up with ...

 
issue

A bug in the JDOQL processor in recent versions of ObjectDB

There seems to be a bug in the JDOQL processor in recent versions of ObjectDB. I've uploaded a "laptop" example to demonstrate the problem. The query in Test1.main should return "ThinkMachine MAX SX 20", but it returns incorrect "Media Central Media 555". Earlier versions (at least up to 2.5.4) correctly return "ThinkMachine MAX SX 20". Regards. Bug Version: 2.6.4 Priority: Normal Status: Fixed Replies: 2 Type:  Bug ...

 
forum_thread

ObjectDB version 2.1 has been released

Version 2.1 has been released: ... ( issue #31 ). Fixed a bug in distinct queries (duplicates due to bad optimization). Fixed a bug in ...

 
forum_thread

member visiting in jpql

baURI is a byte[]; JP QL> select e.baURI.length from URI e where id=82778 JP QL> [ObjectDB 2.2.9_04] javax.persistence.PersistenceException Navigation from 'byte[]' through 'length' is invalid (error 763) at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:636) at util.JPQLcmd.QureyCMD(JPQLcmd.java:43) at util.JPQLcmd.main(JPQLcmd.java:28) Why I can not visit the length attribute? TIA ... length field of arrays is not supported by JDOQL / JPQL queries. You may maintain an ordinary int field (holding the array ...

 
issue

Index Rebuilder

When a new index is added to an existing entity classes that already has instances in the database, it cannot be used in queries, because it starts empty and it is not synchronized with the existing primary data. The Index Rebuilder tool will enable rebuilding indexes, synchronizing their data to the primary data. As a workaround, you can currently use the ObjectDB Doctor to build a new database file, in which such new indexes will be enabled.... has instances in the database, it cannot be used in queries, because it starts empty and unsynchronized with the existing primary ...

 
forum_thread

Global way to set Lazy-loading fetch functionality for all the fields

Hi, for cascading persist, I have 3 choices: - Either locally (@OneToOne(cascade=CascadeType.PERSIST)) - Either at objectdb level (<cascade-persist always="auto" on-persist="false" on-commit="true" />) - Either at JPA global level (orm.xml).   For defining fetch policy, I know the local way to do it (@ManyToOne(fetch=FetchType.LAZY)). Is there any way to do it at objectdb level or JPA global level?   #1 2012-07-15 12:54 Hi, for cascading persist, I have 3 choices: - Either locally (@OneToOne(cascade=CascadeType.PERS ...