About clear

issue

@PrePersist not working correctly

I have a method to calculate some values before persisting to the database. So i annotated it with @PrePersist. If i merge an object the annotated method get's called but all members are on their default values. I only tried it with new objects. So merge get's an object with id = null and therefore shoud behave like persist. (I always use merge) If i set a breakpoint before the em.merge(..) call the object is ok. Inside the @PrePersist method all fields are cleared.  Bug Version: Priority: Normal Status: Fixed Replies: 1 Type:  Bug ...

 
forum_thread

enumeration table? how to on pure jpa?

Hello , I've relational db , and there is some table named enumerations with , some key and values.We will migrate to objectdb. Our problem is , we want to store some keys and values for global application configs. Like; tablename : enumeration table rows: key                value ... like that on pure JPA if possible. Fastest clear way... I've looked some other annotations but i could not ...

 
issue

Issue with cascade delete & add/remove

Hi, Please see the attached sample project (important: classes need to be enhanced as done in the pom.xml file). ... we delete the Contact? Is that cascaded or do we need to clear the collection first, commit that and then remove the Contact? ...

 
forum_thread

How to avoid NULL values on Embedded entities

Hi there. I'm new on this. trying to learn. I'm trying to make a value non nulleable. So, when I try to upload to the DB this field as null, it give me an error. I tried this, but it didn't work: ... if my english is not perfecto, just ask if i'm not clear   Edit: Sorry. Solved. The code was ...

 
forum_thread

Roadmap - no progress - any plans - transparency?

Hi! I have been using ObjectDB for some time, and I'm relatively glad about it. What I'm not so satisfied is that there is no road map for ObjectDB. We see bug fixes and minor adjustments, which is great, but there's nothing about the future. We need to know in which direction ObjectDB is heading, and if it's heading anywhere or just staying in this state forever, as I see it. It would be nice to have more transparency about this topic. I know there are feature requests already made, but they seem to be ignored. ... So, my (and my company's) wish is to see a clear roadmap of ObjectDB. Besides increasing our confidence in your company, ...

 
forum_thread

Thread in BLOCKED state

Hello, Some on my threads stay in BLOCKED state in my thread pool. When i watch the stack trace, i see only just obfuscated object db code. ... The exact problem is not completely clear. A blocked thread is not necessarily a problem. There is an ...

 
forum_thread

InternalError on query of empty database

Hi, I have reasons for sometimes trying to query the database before anything has been created. The problem is the database throws a InternalException when that happens. Is it possible to throw something that identifies that that is the issue, say something like "MissingSchemaException", ie something that clearly shows its because no data of that type has been added? This just makes the exception catching cleaner. Thought thinking about it, it probably needs to be a JPA exception, maybe something like javax.persistence.EntityNotFoundException? #1 2011-07-21 01:39 Hi, I have reasons for sometimes trying to query the database before anything has been created. The probl ...

 
forum_thread

calling persist on an object more than once

results in an error (613) when the transaction is commited: [ObjectDB 2.2.4] javax.persistence.RollbackException Failed to commit transaction: Attempt to reuse an existing primary key value (common.model.UserSession:13) (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo.Transaction$commit.call(Unknown Source)   I submit that there are a number of problems with this: a) the error message is not helpful ... codebase from the persist() c) it's not at all clear to me why this shouldn't be idempotent   ie: if ...

 
forum_thread

Problem with byte arrays in JDO - internal exception

This code generates an internal exception: ... ( ) ; // Clear out existing objects pm. currentTransaction ( ) ...

 
forum_thread

Understanding Database max-threads objectdb.conf Settings Option

These are questions asked in the context of the proposed architecture described in the forum thread titled, "Sample JDO Architecture for Follow Up Questions".   In the objectdb.conf file (attached to forum thread mentioned above), I set Database max-threads.  In the documentation, it was not completely clear to me if this setting controlled how many internal threads ObjectDB uses, or if ObjectDB is doing some sort of queue/locking whose depth is determined by this setting (and entries are per thread request). ... In the documentation, it was not completely clear to me if this setting controlled how many internal threads ObjectDB uses, ...