About match

manual

Strings in JPQL and Criteria Queries

Explains string expressions in JPQL queries, including LIKE, LOCATE, LOWER, UPPER, TRIM, CONCAT and SUBSTRING.... The left operand is always the string to check for a match (usually a path expression) and the right operand is always the pattern ... (for any c.name value). To match an actual underscore or percent character it has to be preceded by an ...

 
forum_thread

Object comparation never matches

Hi! I'm trying to compare 2 identical objects in SELECT with no success: @Embeddable public class PhoneNumber implements Serializable {     int countryCode;     long number;   Which is a part of Customer object: #1 2013-03-30 16:36 Hi! I'm trying to compare 2 identical objects in SELECT with no success: @ Embeddable ...

 
forum_thread

Recovery file does not match db file

Just rebooted my production server, which had been running fine for months. When it came up, these errors started: ObjectDB 2.3.1_03] javax.persistence.PersistenceException Recovery file '/auctionologies/java/storage.odb$' does not match db file '/auctionologies/java/storage.odb' (error 145)  at com.objectdb.jpa.EMF.createEntityManager(EMF.java:176) at javax.persistence.EntityManagerFactory$createEntityManager.call(Unknown Source) Note: other than reboot the machine, I didn't do anything else. ... file '/auctionologies/java/storage.odb$' does not match db file '/auctionologies/java/storage.odb' (error 145)  at ...

 
issue

NoResultException: No matching results for a unique query

I am very often getting a "com.objectdb.o._NoResultException: No matching results for a unique query" when modifying my already persisted entities within a transaction. I cannot replicate it however because it happens infrequently. The weird thing is that the entity nevertheless gets comitted perfectly right and all data is correctly written so I have no clue what's going on!?? Here's the stacktrace (copy+paste from debug output): Bug Version: Priority: Normal Status: Closed Replies: 6 Type:  Bug ...

 
forum_thread

Documentation problem - license does not match implementation

The license page says: "ObjectDB can be downloaded and used at no cost (including commercially) with the restriction of maximum 10 entity classes and one million entity objects per database file." I was well into a rather large project when I discovered, much to my horror, that the free license does not allow 10 entity classes.  It allows a total of 10 persistable classes - entity and embeddable combined.  I will now probably have to drop ObjectDB in favor of some other JPA provider. #1 2012-08-25 07:06 The license page says: "ObjectDB can be downloaded and used at no cost (including commercially) with the restrict ...

 
manual

Database Schema Evolution

Explains how ObjectDB handles automatically schema changes. Modifications to entity classes that do not change their persistent field definitions (their schema) are transparent to ObjectDB. This includes adding, removing and modifying constructors, methods and non persistent fields. However, additions, deleti ...

 
api-jdo

setResultClass(cls)

Specify the type of object in which to return each element of the result of invoking execute or one of its siblings.(Method of javax.jdo.Query)

 
api-jdo

javax.jdo.PersistenceManagerFactory

The PersistenceManagerFactory is the interface to use to obtain PersistenceManager instances.(Interface of JDO)

 
forum_thread

JPA 2.0 Criteria API: (When) Fully supported ?

An excerpt from the website of a 3rd party vendor which tries to support JPA 2.0:   "The primary difference between JPA 1.0 and JPA 2.0 implementations is how data is fetched: the JPA 1.0 implementation creates a JPQL query string for fetching while the JPA 2.0 implementation uses Criteria API.   Tested JPA 2.0 providers #1 2012-02-23 13:27 An excerpt from the website of a 3rd party vendor which tries to support JPA 2.0:   "The prim ...

 
forum_thread

Order in WHERE Clause affects behaviour on DATE/DATETIME columns

Quick example:  public class MyClass { @Column(name = "myText") String myText; @Temporal(TemporalType.TIMESTAMP) @Column(name = "myDate") Date myDate; } Now, when querying the db with: ... Parameter value [%myQuery%] did not match expected type [java.util.Date (n/a)] because I haven't declared the ...