Is there any known performance issues with either self-reference or circular reference?

Hi, OpenJPA 1.0.0 Oracle 10g R2 Is there any known performance issues with either self-reference or circular reference? When I analyze Oracle SQL trace, it reports the CPU and number of queries way too high for tables which have only < 10 rows! THE PERSISTENCE CLASSES: public class Taxonomy ..

Re: Detached instances in query parameters

Please check out my post: http://www.nabble.com/Persistent-entities-pass-as-params-to-JPQL-queries-MUST-be-attached--Query.getSingleResult%28%29-bug-or-expected-behavior--td12748830.html#a12748830 -Frank Zdenek Machac wrote: > > Hi, > > we use OpenJPA in WebLogic 10.0 server but we have expe

Re: Oracle blob exception

Rúben, If it's Oracle 10g, it's fixed in the latest Oracle JDBC driver 10.2.0.3.0. (I don't think you need to specify maxEmbeddedBlobSize) -Frank Rúben Cabaço wrote: > > Hi, > > I am trying to write a byte[] annotated as a Lob to an Oracle > database but I keep getting: > Caused by: >

Re: [DISCUSS] Release planning

ick > > On Feb 1, 2008 3:36 PM, frankca <[EMAIL PROTECTED]> wrote: >> >> >> >> Craig L Russell wrote: >> > >> > Are there other features in 1.1.0 that are urgently needed and that >> > can be pulled into 1.0.2? >> > >>

Re: [DISCUSS] Release planning

Craig L Russell wrote: > > Are there other features in 1.1.0 that are urgently needed and that > can be pulled into 1.0.2? > I'd really appreciate if this critical bug get fixed in 1.0.2 which is already fixed in 1.1.0 TRUNK (http://svn.apache.org/viewvc?view=rev&revision=584463): http://ww

Data cache usage?

Hi, I'd like to test data cache by simply enable for read-only objects, however, it seems to be slower than cacheless. 1) Can someone please share your experience or usage example that verifies improving performance? 2) Can I annotate @DataCache at superclass (@MappedSuperclass)? Here's how I

Re: Unique constraint violated using Oracle sequence to generate ID only when multi-threaded.

FYI: I opened the issue# OPENJPA-466 frankca wrote: > > Hi, > > First, I understand the following is thread-safe which I mean OpenJPA > always asks the database sequence for the next value: > @Id > @SequenceGenerator(name = "FooSeq", sequenceName = &

Re: Programmatically pagination does NOT work with OpenJPA 1.0.1

ENJPA-378 >> > >. >> > >> > The latest trunk snapshots don't have the bug, but the fix would need >> > to be backported to 1.0 branch if a fix is needed for that line. >> > >> > Can you open a JIRA so we can track it? &

Unique constraint violated using Oracle sequence to generate ID only when multi-threaded.

Hi, First, I understand the following is thread-safe which I mean OpenJPA always asks the database sequence for the next value: @Id @SequenceGenerator(name = "FooSeq", sequenceName = "seq_foo") @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "FooSeq") private Long

Re: Programmatically pagination does NOT work with OpenJPA 1.0.1

(long) 2] -Frank Patrick Linskey-2 wrote: > > What SQL do you see? Is this a regression from 1.0.0, or something > that you're running into for the first time? > > -Patrick > > On Nov 12, 2007 4:46 PM, frankca <[EMAIL PROTECTED]> wrote: >> >> Prog

Programmatically pagination does NOT work with OpenJPA 1.0.1

Programmatically pagination does NOT work with OpenJPA 1.0.1 i.e. using EntityManager.setFirstResult()/setMaxResults(). Sorry, I don't have time to package a test case for now. -Frank -- View this message in context: http://www.nabble.com/Programmatically-pagination-does-NOT-work-with-OpenJPA

Re: Persistent entities pass as params to JPQL queries MUST be attached? Query.getSingleResult() bug or expected behavior?

e a managed instance to understand how to handle object identity) >> or you are accessing persistent fields (in which case we must be >> hooked into the object in order to dig into it). >> >> IIRC, this behavior is not defined in the spec -- I think the spec &

Re: Persistent entities pass as params to JPQL queries MUST be attached? Query.getSingleResult() bug or expected behavior?

a pretty convoluted way to always return no > results. > > [Frank Le] I totally agree, since this behavior is not in the spec or > OpenJPA manual, this will cause lot of debug from developers. > > -Patrick > > On 9/17/07, frankca <[EMAIL PROTECTED]> wrote: >> &

Re: Persistent entities pass as params to JPQL queries MUST be attached? Query.getSingleResult() bug or expected behavior?

hooked into the object in order to dig into it). > > IIRC, this behavior is not defined in the spec -- I think the spec > does not permit queries that directly compare entities. > > -Patrick > > On 9/17/07, frankca <[EMAIL PROTECTED]> wrote: >> >> Hi, >&g

Persistent entities pass as params to JPQL queries MUST be attached? Query.getSingleResult() bug or expected behavior?

Hi, I have simple query with Foo and FooType are persistent classes and name is string type: (1)@NamedQuery( (2)name = "Foo.findByTypeAndName", (3)query = "SELECT e " + (4)"FROM Foo e " + (5)"WHERE e.fooType = :fooType " + (6) "

Never mind. I resolved it.

Never mind. I resolved it. frankca wrote: > > Hi Craig, > > Because the default value is 255 which doesn't apply to CLOB, however, it > doesn't make any different if don't define it. > > Here's from Kodo KB: > A normal string field was ma

Re: ERROR: declares a column that is not compatible with the expected type "clob"

really needs to be a good application-specific value. > > Craig > > On Sep 12, 2007, at 10:51 AM, frankca wrote: > >> >> Hi, >> >> Does anyone run into this error: >> exception is >> org.apache.openjpa.persistence.ArgumentException: >> &quo

ERROR: declares a column that is not compatible with the expected type "clob"

Hi, Does anyone run into this error: exception is org.apache.openjpa.persistence.ArgumentException: "com.inxight.mdr.dao.model.Sentence.text" declares a column that is not compatible with the expected type "clob". Column details: Full Name: sentence.text Type: integer Size: 0 Default: null Not