6 | ODB IndexActivation NullPointerException other hint? btc_es BTC EmbeddedSystems Small update: We think a workarround (but not usefull |
6 | Entity can be found by find() but not by query it then this could be very helpful in understanding this situation. support Support It seems that the hint with the deactivated |
6 | Web Framework Recommendation for leveraging JPA + ObjectDB + ObjectDB" couple successfully in conjunction with a contemporary Web Framework ? Any hints/recommendations |
6 | @Lob @Basic(fetch = FetchType.LAZY) is loaded when it's not needed Myachikov FetchType.LAZY is a hint that JPA implementations are allowed to ignore. Currently ObjectDB |
6 | Issue with Casting / Joins, maybe this can be solved by adding a new ObjectDB specific hint. support Support hi, okay, asked |
6 | Is there any restriction when using fetch=FetchType.LAZY ? (although it is only a hint in JPA and ObjectDB is allowed to ignore it and load data eagerly). On detach some |
1 | References to objects of missing obsolete entity classes not occur with objectDB version 2.8.0_4. Did you change anything and do you have any hint as |
1 | Use temporary files to enable very large transactions and file-size usage between in-memory(<2GB) and temporary file(8GB)? Hint: We currently use version |
1 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) (even though it is allowed by JPA - lazy is only a hint), allocating IDs during persist, initialization |
1 | InternalException when using MEMBER OF on a large list in a query. Also thanks for the hint with long keys. Can you give us a recommendation as we can represent the Key |
