ObjectDB Database Search

when ordering the results of some projection when the order by expression is different (though logically equivalent) to the projection expression . Here is the example: @Entity public class Location ... ;  }     } Exception thrown: Invalid order expression 's_location' for distinct

HD), etc... 5. Evaluation of expressions when editing fields - It would be very useful to be able to enter a Java expression into a field. For example, suppose you have a User entity with a password field. I would like to enter SHA1.hash("mypassword");  You might use beanshell for the expression

other reachable managed entity object. All the expressions that you wrote are valid, if x is a managed ... transparent activation / retrieval). When using ObjectDB you can also use these expressions in queries ... handling such expressions . Indexes are supported in handling more conventional collection

may be with the expression   c.bList.val . Path expressions are considered as INNER JOIN by JPA, although apparently it makes sense to consider path expressions in LEFT JOIN FETCH differently. support Support

queries (as an extension to JPQL and JDOQL) you can use the Normalizer expression directly in the query ... ; I've tried to add the normalizer expression into order by clause, but it thorws this exception

query but without all the lower expressions . Similar queries but with fewer expression in the OR

. So if the parameter y is a collection the expression y.b is invalid. support Support

selection element in my tuple selection only? I.e. I don't want to every selection expression

for JRebel, it just is great for my work.) I invite further expressions of support for compatibility

the in-memory objects? There are cases where the JPQL syntax is more expressive than operating

criteria in debugger we get the correct expression : SELECT DISTINCT $1 FROM MyEntity $1 WHERE ((TYPE ... .objectdb.o.UserException: Invalid order expression '$2' for distinct results at com.objectdb.o.MSG.d ... .criteria.CriteriaQuery; import javax.persistence.criteria. Expression ; import javax.persistence.criteria

FETCH to act as LEFT JOIN in path expressions . Updated the PDF manual. Fixed a possible deadlock ... (inverse) relationships. Fixed a bug in using IN expression in criteria queries . Fixed processing an IN(:param) expression in JPQL queries.

their subfields? Because I've assumed that in such cases, the expressions are not evaluated

Added support of embedded path expressions  to  mappedBy  fields ( issue #2917 ) Fixed the SectionClassifier retrieval bug ( issue #2912 ). Fixed log file location for some server log messages ( issue #2914 ).