5 | Type xxx is not found (error 301)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 |
5 | Storing objects problem include any indication that the child devices are not empty. Please follow the posting instructions |
5 | impossible to drop a table with 50 million objectswhen trying to execute in explorer (max heap size 1GByte) delete from LogEntry l it comes up with a Java heap error after 20 minutes of executing. How to empty such a table ? hgzwicker Hans-Georg Zwicker This may be because the transaction size is limited by the heap size. You can try deleting |
5 | First query before any of the object has been stored, and coded to handle that as an empty result. What's really getting thrown is the more general |
5 | Getting com.objectdb.o.UserException: with ObjectDB 2.4.3_01 by specifying an empty path. support Support |
5 | Replication failed_01). Other ideas: verify that both servers on 6136 and 6000 are running, start with an empty |
5 | @ElementCollection query returning extra result per element in collection being confused about JPA2 criteria again. Here is the example output, with a new DB (empty db |
5 | Database(*.odb) file size on disk are reused but the the file not resized. The database is at the end empty again, but larger than the initial |
5 | Changes in detach behaviour? and the em. With 2.3.5_04 I get an empty detached user object back. Only the id is correct |
5 | Database absolute filepath) and create a new empty database. By default it works only for database files with the temp / tmp file name extensions. support Support |
