 13 | , Path, Selection, TupleElement A root type in the from clause. Query roots ... (Class type) Perform a typecast upon the expression, returning a new expression object. Perform a typecast upon the expression, returning a new expression object. This method does not cause type |
13 | for this and get a JdoDataStoreException: Too many persistable types (>10) - exceeds evaluation limit ... ObjectDBWriting Join Tables" transaction- type="RESOURCE_LOCAL">
com.objectdb.jdo.Provider ... >
type="RESOURCE_LOCAL |
13 | the CultureRqst leads to the following exceptions:
[ObjectDB 2.2.8_08] javax.jdo.JDOUserException
Type com ... that all the relevant types for ObjectDB are available only in one Eclipse bundle. Hello, I think ... it Exception in thread "main" [ObjectDB 2.6.4_07] javax.jdo.JDOUserException Type java.util.ArrayList |
13 | "main" [ObjectDB 2.3.2] javax.persistence.PersistenceException
Unsupported auto value type java.lang ... (NetworkInformationDatabase.java:71)
Caused by: com.objectdb.o.UserException: Unsupported auto value type java.lang.String ... ;
You cannot use @GeneratedValue for string Id only for numeric Ids. Id fields whose type is string have to be assigned a value by the application. kiki |
13 | Hello, can you add an option to the Class Enhancer to enhance all persistable types and ignore the NON persistable types. Like the Load Time Enhancement. A new argument (undocumented yet) was added ... ... It should exclude enhancing non persistable types (i.e. persistence aware classes) as in using Enhancer |
13 | to generate dynamic type com.quasado.galaxy.foundation.api.language.LanguageContext I am curious why he does even try to generate dynamic type?? Can he simply ignore such things and enhance ... generating a dynamic synthetic type. Usually it succeed but in some cases it fails |
13 | without parsing the exception text. It would be very nice if this particular exception were a type ... .summaryframework.entities.daos.SummaryArchiveDAO:206 -> Query failed due to TEX: Type ... could be different. Thank you very much for your help! This issue is resolved. Introducing the type |
13 | The error: Type User is not found (error 301) occurs when I query the db for a type before any instances of that type have been persisted, e.g.:
return em.createQuery ("SELECT a FROM User a").getResultList (); What I was expecting was an empty list, not an error. Is there some enhancement |
13 | you can persist any Serializable type by setting the configuration. There is no point in persisting most of the non serializable types such as Thread, because when retrieved from the database it will not ... any collections either. If this feature was in place it wouldn't matter what the object type is, surely? ThreaT |
13 | Hi, Is there a reason why we can't persist an object with a field of type EnumMap in ObjectDB ... type if you enable this ability in the configuration. But using this feature is not recommended. ObjectDB provides better support (i.e. more efficient and portable) for specific types (including collections and maps), based on the JPA specification. EKK |
