RE: Oracle9i Blob Field Access

It turns out this particular problem was being caused by 'DISTINCT' being set in the criteria. Removing distinct solves my problems... P -Original Message- From: Nase, Paul R. [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 11:16 AM To: 'ojb-user@db.apache.org' Subject

Oracle9i Blob Field Access

I am having some strange issues with retrieving a blob field. I am using an Oracle9i DB with the oci8(not thin) JDBC driver. I am also at OJB 1.0.1. There are two parts to this problem. 1) When I go to access my object containing a blob field using getObjectByIdentity(), it fails the first

ClassDescriptor.updateLockingValues() implementation in 1.0.1 vs. 0.6

Hi, I am currently attempting to migrate our application from 0.6 to 1.0.1. One of our test cases caught a small change in the ClassDescriptor implementation in which I am confused as to why this would need to be done. Here is the original code (updateLockingValues()): //

RE: ClassDescriptor.updateLockingValues() implementation in 1.0.1vs. 0.6

). But after reading the java.sql.Timestamp javadoc I tend to agree with you. Will try to add an test case for this issue. Which DB do you use? regards, Armin Nase, Paul R. wrote: Hi, I am currently attempting to migrate our application from 0.6 to 1.0.1. One of our test cases caught a small

RE: ClassCastException in QueryReferenceBroker.

confirm this ? what class is returned by collectionField.get(owner) ? jakob Nase, Paul R. schrieb: We are currently on OJB RC6 and cannot move to OJB 1.0 at this time due to product release schedules. During multi-user/load testing, we occasionally see the following ClassCastException occurring

RE: OJB Cache and materialization.

and listeners if (insert) Armin Waibel wrote: Hi Paul, I will have a look at this. Stay tuned! regards, Armin Nase, Paul R. wrote: Hi, We are encountering a problem with our cache materializing half-baked objects when under a heavy multi-user load. We are currently

RE: OJB Cache and materialization.

#localClear() was called (and reset the counter) on PB.abort/commitTransaction and PB.close(). This should guarantee that InternalCache is always in sync. What do you think? regards, Armin Nase, Paul R. wrote: Thanks Armin, It looks good (works too), but I have one issue with the fixes you

OJB Cache and materialization.

Hi, We are encountering a problem with our cache materializing half-baked objects when under a heavy multi-user load. We are currently using OJB RC5 and are not in a position to move to 1.0.1 yet, although in the future we would like to. We also have a JCS cache configured. Our problem occurs

RE: Query with criteria - like using '%' or '_'

based on your solution and additional LikeCriteria. jakob Nase, Paul R. wrote: Jakob, Perhaps I am misunderstanding your question. When you say why can't we add the ESCAPE to the search argument?, do you mean add it like the following? criteria.addLike(*\\%* ESCAPE '\\') // to search

RE: Query with criteria - like using '%' or '_'

Users List Subject: Re: Query with criteria - like using '%' or '_' hi paul, i'm sorry i forget that ojb manipulates the criteria in addLike. imo it would be the best to pass the criteria withou any modifications to the dbms. what do you think about this ? jakob Nase, Paul R. wrote: Adding

RE: Query with criteria - like using '%' or '_'

'%' or '_' hi paul, i'd prefer to have the whole escape handling in one place, in critria. also i do not know if the escape handling is platform independent. jakob Nase, Paul R. wrote: It shouldn't matter what db is being used, I should be able to find any fields containing

RE: Query with criteria - like using '%' or '_'

addLike(your_attribute,P%) hth jakob Nase, Paul R. wrote: I would like to perform a query where a description could have a '%' or an '_'. Is this possible using QueryByCriteria? Example: ID DESCRIPTION --- 1 40% Member Discount 10001