About literal

21-30 of 43Refresh
Forum
3

Query fails with numerical values > 2^31

) delete from DataRecord p where p.TimeOfDeletion < 4147483648 This fails with "invalid numerical literal ... .TimeOfDeletion > ==> 1410521635503 <== javax.persistence.PersistenceException Invalid numeric literal ... .Thread.run(Thread.java:745) Caused by: com.objectdb.o.UserException: Invalid numeric literal
Forum
3

Object as parameter results in exception

the primary key is used as a literal, which means that the query has to be compiled every time and the query program cache cannot be used. Maybe ObjectDB should optimize such queries replacing literals ... this query the way it is? Please ignore my original post - the literals are a pretty bad idea
Forum
2

Searching lists within objects

()) with char literal ('5') ObjectDB considers the literal as character rather than as a string. Only in ... a string parameter instead of a literal. Test 7 fails because the query is executed using an index
Forum
2

Problem on JPA Merge Entity.

] SingleValueConstraint [comparator=ERGOKeyword [id=56, preferedName==], value=TimePoint [literal=01-01-2000 ... ] SingleValueConstraint [comparator=ERGOKeyword [id=56, preferedName==], value=TimePoint [literal=01-01 ... [literal=10-10-1900]] Hi, My apologies, in fact I did not change the version in the configuration file
Result
2

ObjectDB version 2.3.5

. Fixed using type operator and literals in client server queries (issue #605). Fixed eager fetch issues. Fixed a bug in using type literals in queries. Fixed a bug in passing a new entity object
Forum
2

query on calendar class

. System still throws Caused by: com.objectdb.o.UserException: Invalid date literal {t c.start} or erros ... mentioned in your post: The {} syntax is for literals, so it cannot contain variables or parameters. In
Forum
2

Using date in where clause

) with a string literal ("07-25-2013"). Replace the string with a date literal or a parameter. n126961
Result
1

ObjectDB version 2.4.0

not using LIKE's ESCAPE when an index is used. Fixed a bug in parsing time literals in queries. Fixed
Result
1

ObjectDB version 2.5.0

entity instead of a PK in find (retrieval by example). Added support of using list of literals in
Forum
1

Criteria Query results in a NoResultException instead of returning object

();   OK. Your program demonstrates a bug in the new mechanism of ObjectDB 2.2.4 that converts literals