ObjectDB Database Search
51-100 of 108 resultsjakarta.persistence.ConstructorResult of the intended constructor, in order. Since: Jakarta Persistence (JPA) 1.0 Additional JDK methods inherited | |
jakarta.persistence.Converts Persistence (JPA) 1.0 Additional JDK methods inherited from java.lang.annotation.Annotation java.lang | |
jakarta.persistence.Converter type. Default: false Since: Jakarta Persistence (JPA) 1.0 Additional JDK methods inherited from java | |
jakarta.persistence.ColumnResult Since: Jakarta Persistence (JPA) 2.1 Additional JDK methods inherited from java.lang.annotation | |
jakarta.persistence.Embedded with no members/elements. Additional JDK methods inherited from java.lang.annotation.Annotation java.lang | |
jakarta.persistence.Embeddable. Additional JDK methods inherited from java.lang.annotation.Annotation java.lang.annotation.Annotation | |
jakarta.persistence.Entity Additional JDK methods inherited from java.lang.annotation.Annotation java.lang.annotation.Annotation | |
jakarta.persistence.EmbeddedId/elements. Additional JDK methods inherited from java.lang.annotation.Annotation java.lang.annotation | |
jakarta.persistence.DiscriminatorColumn Persistence (JPA) 1.0 Additional JDK methods inherited from java.lang.annotation.Annotation java | |
jakarta.persistence.ElementCollection, defaults to LAZY . Default: FetchType.LAZY Since: Jakarta Persistence (JPA) 1.0 Additional JDK methods | |
jakarta.persistence.DiscriminatorValue value default is the entity name. Since: Jakarta Persistence (JPA) 1.0 Additional JDK methods inherited | |
jakarta.persistence.EntityResult of the entity instance. Default: "" Since: Jakarta Persistence (JPA) 1.0 Additional JDK methods | |
jakarta.persistence.EntityListeners listener classes Since: Jakarta Persistence (JPA) 1.0 Additional JDK methods inherited from java | |
jakarta.persistence.ExcludeSuperclassListeners . Annotation Elements This is a marker annotation with no members/elements. Additional JDK methods inherited | |
jakarta.persistence.FieldResult Persistence (JPA) 1.0 Additional JDK methods inherited from java.lang.annotation.Annotation java.lang | |
jakarta.persistence.Enumerated used in mapping an enum type. Default: ORDINAL Since: Jakarta Persistence (JPA) 1.0 Additional JDK | |
jakarta.persistence.ExcludeDefaultListeners Elements This is a marker annotation with no members/elements. Additional JDK methods inherited from | |
jakarta.persistence.EnumeratedValue (JPA) 3.2 Annotation Elements This is a marker annotation with no members/elements. Additional JDK | |
Explorer in 2.3 data and Strings. After playing with it for a while, here is a list of additional features I'd love ... to the database. Again, many thanks for a tremendously useful new addition to ObjectDB. Carl   ... to split the results by id ranges (adding additional top levels to the tree, similarly to viewing | |
Replaying recorded requests... a PersistenceManagerFactory? Dave dmoshal David Moshal Couple of additional points: 1. the database ... addition , please verify that you close the database with PersistenceManagerFactory's close ... so that's one problem. I have been using /WEB-INF/objectdb.conf - is this the wrong location? In addition | |
ObjectDB throws `NullPointerException` in internal code (`com.objectdb.o.ENH.b`) be able to upload files if you have any additional relevant information to share. support Support Hi ... , could you share additional details from your experience? For instance, was there a specific class ... , so the underlying cause of the issue remains unclear. However, if additional type 2 schema changes | |
Mismatch client-server protocol prefix Moser The last two stack traces do not mention ObjectDB. In addition to checking the database file ... Tomcat. In addition we converted our Spring configuration from xml to configuration classes ... Yesterday I upgraded to Version 2.6.2_06. In addition I compared the spring configuration | |
Exception on creation when running multithreaded are of type CDI and in addition , as a setup for the test I'm creating another 3 objects of type PDI ... which is also extending the same class as CDI and PDI with some minor additions . In the same test that fail I | |
Problem on JPA Merge Entity. which methods it is true and in which false? In addition , verify that the same EntityManager is used | |
Pessimistic Lock Timeouts setting tests, but if you can provide additional tests, particularly if they demonstrate problems | |
like operator (String) isn't a problem. The GUI related methods will add implicit a '%' character. Additional hint:  | |
query on calendar class duplicating this information into an additional persistent field. The comparison failed because of comparing | |
Double persist of Entity field with Cascade.ALL Explorer. Let me also mention an additional observation I made: if the new chapters are created and added | |
ObjectDB Roles and Groups inheritance from other virtual users (in addition to $default ) in next versions - will this help | |
StackOverflowError after commit side), since it does not match the stack trace. In addition , this is only a partial stack trace. Please find | |
Activation error on Schema change addition , as reported in another forum thread , changing network may also require reactivation. support | |
Level 2 cache not hit in @ManyToOne, retrieving them later may require additional round trips. Regarding problem 1, if Item is the owner | |
OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011) should include a more detailed stack trace. Could you please send it? In addition , if this is a new error | |
Cascading makeTransient the memory and it represents additional unwanted memory consumption. I tried to solve that via calling pm | |
SSL cannot connect from client StackOverflow error and didn't saw any additional option needed. It fails on method PersistanceManagerFactory | |
Populating entity id before transaction commit Hi, I have a question about populating auto generated id before transaction commit. We are using OBD with Spring and transactions are managed by Spring. The problem is, that we have custom annotation that wraps some of those functions to do additional work. But this annotation is executed before | |
Failed to commit transaction: Attempt to commit a rollback only transaction-server mode to embedded mode is the solution. support Support In addition - the complete stack trace from | |
Persist not working when ObjectDB and another db is used in the same application (through spring) with different tx managers(value ="myTxManager", readOnly = false) public void addObject() { ... } In addition | |
retrieval again and again started but probably worth trying) + improved log, which expects to add additional stack traces to the log in ... it might be helpful. Any other additional information (see #13 and #15 above) may also help. If the query ... . If there are any additional issues, which are not related to the original posts (#1 to #7), i.e | |
ArrayIndexOutOfBoundsException on flush the database in question and the objectdb logfile via ftp in case it can shed any additional light ... the additional stack traces do not provide more info and replaying the recorded transactions fail. I | |
Best practice for history tracking addition , every post should discuss one topic, so I think it would be better to separate the last | |
InternalException: null Build 2.6.1_05 includes an addition of a synchronized wrapper, which might have been missing in | |
[ObjectDB 2.6.7_04] Unexpected exception (Error 990) working, but build 2.6.7_05 includes some addition that maybe can help. support Support 2.6.7_05 works | |
combined index not used additional statistic information. To benefit from these changes ObjectDB must collect that statistics | |
JDO PersistenceManager.getSequence() returns null sometimes sequence strategy): An additional minor issue is that ObjectDB appears to ignore the package name | |
objectdb seems to do explicit gc which leads to excessive CPU usage it is really interesting, there is only the jetty server used in addition , we'll go on investigating that hgzwicker Hans-Georg Zwicker | |
Server crash - Mismatch client-server protocol prefix if you had a way to obtain it. In addition , you just reported another issue today. Is it just a coincidence | |
InternalException caused by OOM: Metaspace ) If the JVM MaxMetaspaceSize parameter is set you may want to try increasing the limit. In addition | |
Cascade.ALL with LAZY fetchtype does not clean up all references on remove Hello, I have a tree of entity classes that reference others using Cascade.ALL in combination with FetchType.LAZY. If I now delete a root entity using EntityManager.remove all leaf nodes will not be deleted. This only applies to the leaf nodes. If I add an additional the behaviour changes | |
ObjectDB for .NET (C# / VB) Work on porting ObjectDB to .NET has started. The new file format of ObjectDB 2 has been carefully designed to support multi platform in general and .NET specifically. The same database file should be accessible from both Java and .NET. In addition , when using client server mode, the client |