Internal Website Search

111-120 of 200 resultsRefresh

order by string with numbers

> ORDER BY CAST(SUBSTR(username FROM 4) AS UNSIGNED) ASC Using JPQL SELECT u FROM Users u ORDER BY SUBSTRING(u.username,4)*1 ASC If you have other alternative ... ; mlevinspuhl Marcel Levinspuhl It seems that this is not supported by JPA criteria

how to query by properties of onetomany relations? (Error 990)

> [ObjectDB 2.2.4] Unexpected exception (Error 990)   Generated by ... about the error message - it should be replaced by a more descriptive error message in future versions. ObjectDB can enforce using standard JPQL by setting

Master database switching to read-only mode, possibly caused by slave failure

databases have failed, slave became unresponsive and the master switched to read-only mode. By the look ... ) .............................................................. Caused by: com.objectdb.o.UserException: Connection ... .odb' is closed by 30752@hardhead We did not see anything wrong in the monitoring data

UserException: Package com.example.model is not found by the enhancer

: Package com.example.model is not found by the enhancer It occurs on this line:by different class loaders and the Enhancer do not have access to the classes. Enhancing by invoking the Enhancer from the application (as demonstrated in your post

Need help to analyse very high memory usage by objectdb (PRU, SEV, VAL[])

a "GC overhead limit exceeded" exception. Nearly 90% of the memory are taken by com ... /domain/objectdb.com Forum Thread Need help to analyse very high memory usage by objectdb objects (PRU, SEV, VAL[]) has been created. btc_es BTC EmbeddedSystems This may be caused by

Extending model by "common entity"

.Thread.run(Thread.java:662) [na:1.6.0_22] Caused by: java.lang.ClassNotFoundException: pl ... Lukasz Walkowski This schema change should be handled by ObjectDB - so the exception is unexpected. Maybe you have to restart the server (I see that the stack trace is generated by

NULL prefered in ORDER BY?

Hi! Is there a way to NOT prefer NULL in Order BY? I.e. assume this: @Entity class Hint {     private String name ... > SELECT FROM Test ORDER BY hint.name It orders ASC like

Bug: ClassCastException by retrieval

; tNode tn3 = em.find(tNode.class, 1);   System.out.printf("find by retrieval : %s %n",tn3.getTa ... , l, d, 2] [H, e, l, l, o, W, o, r, l, d, 2] find by retrieval : H Arrays : [H, e, l, l, o, W, o

Alias not used in ORDER BY

)) I would have expected the alias to be used in the ORDER BY clause, something like SELECT $1, UPPER($1.someStringProperty) AS TEST FROM T ORDER BY TEST ... , UPPER($1.someStringProperty) AS TEST FROM T ORDER BY UPPER($1.someStringProperty)

JPQL support for mapped by (inverse) collections

, collection operators and methods (IS EMPTY, SIZE, MEMBER OF, IN) are currently not supported for mapped by (inverse) collections. These operations are supported for direct (not mapped by) collections. Navigation and JOIN is supported for both direct and mapped by collections.