About size

issue

ObjectDB can't be activated

Hello, we are trying to activate objectdb on a virutalized debian 7 server, but do not have any success. Steps we made to activate the server: ... Maximum file size: 32 MB 0 ...

 
forum_thread

Duplicate Entity class names causes Exception in Query

I have two Entities which have the same class name but reside in different packages, only one of them is mentioned in the persistence.xml. I a NamedQuery I use the unqualified class name of one of these entities. If I execute that query I get an exception;   ... Maximum file size: 32 MB 0 ...

 
issue

Issue with DISTINCT Select

It is getting more and more frustrating :( We've introduced distinct select instead of regular selection in our code (no changes else) and suddenly receive invalid identifiers in queries exceptions in various queries. Here's the stacktrace: ... Maximum file size: 32 MB 0 ...

 
forum_thread

UserException - Object User#2 belongs to another EntityManager

Hi! Scenario's steps: 1. User goes to his profile, a JSF page. 2. @RequestScoped CDI bean UserDataB loads the current user of the session at each request, by using @Stateless bean UserC#findUserById(Long id) 3. JSF page's @RequestScoped CDI bean AnotherB loads trades of that user, by using @Stateless bean TradesC#findTradeByClient(User u). ### UserC and TradesC have their own @PersistenceContext EntityManager with the same unitName. ... Maximum file size: 32 MB 0 ...

 
forum_thread

Entity is not related to ObjectDB, but i get exception from ObjectDB

Here is the description of the problem we are facing:
We have an entity DialogActionNew which previously was located in ObjectDB and recently has been transferred to PostreSQL. We are using ORM Hibernate
When getting this entity from PostgreSQL with the key EntityManager.find(id), we receive another entity - DialogNew, which has an exception: ... Maximum file size: 32 MB 0 ...

 
forum_thread

Selective merge/cascade of detatched entity

I'm having an issue with my application, and I'm hoping you guys will be able to help. Please forgive typos and obvious errors, I'm having to retype from a non-internet connected network. A contrived example is: ... Maximum file size: 32 MB 0 ...

 
forum_thread

InternalError on multiple AND and JOIN Query

Hi, Using objectdb 2.2.8_06. Running the following query: SELECT DISTINCT $1 FROM CDI $1 JOIN $1.contactDetails $2 JOIN $2.addresses $3 JOIN $3.attributeList $4 JOIN $2.phoneNumbers $5 JOIN $5.attributeList $6 WHERE ((($4.name='suburb') AND ($4.valueAsString='Los Angeles')) AND (($6.name='areacode') AND ($6.valueAsString='310'))) Getting: ... - Naming appender as [SIZE_BASED_ROLLING_APPENDER] 09:30:08,912 |-INFO in ... |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[SIZE_BASED_ROLLING_APPENDER] - Active log file name: size_example.log 09:30:08,924 |-INFO in ...

 
forum_thread

Should derived fields of an EmbeddedId be manually maintained by app code?

If I have an Entity which has a primary key which is derived and I am implementing it using @EmbeddedId, am I responsible for maintaining the derived fields of the @EmbeddedId? I could not find anything in the JPA 2.0 spec http://download.oracle.com/auth/otn-pub/jcp/persistence-2.0-fr-oth-JSpec/persistence-2_0-final-spec.pdf?e=1317047713&h=54831c176e81a244a4c309e13eba0b27 which tells me what to expect. ... Maximum file size: 32 MB 0 ...

 
forum_thread

Unexpected internal exception during set field of an Embeddable to null

Hello, we get an Unexpected internal exception and have no idea what goes wrong. We can reproduce (mostly) the error in a very big use case. In the big use case and we create and persist millions of SignalValueImpl objects (Embeddables). Partly as in the stack trace an Embeddable contain another Embeddable. It seems like that we can't reproduce the problem in smaller use cases with less objects. Stack trace: ... Maximum file size: 32 MB 0 ...

 
forum_thread

Problem with distinct select, order by and equivalent alias/attribute path

Hi, while working with a (standard-)JPA-query generating framework we run into an exception when ordering the results of some projection when the order by expression is different (though logically equivalent) to the projection expression. Here is the example: ... Maximum file size: 32 MB 0 ...