RE: Bizarre object update error

2004-08-02 Thread jonathan . lister
Hi Mindy - this is an Oracle error message direct from database server which has run out of shared pool memory. You can allocate more memory to the shared pool via 'large_pool_size' setting in Oracle configuration (on the Oracle server, nothing to do with OJB). -Original Message- From:

newbie: using timestamp in criteria, compound primary key

2004-07-16 Thread jonathan . lister
I am trying to limit a select from a logtable to the last so many days worth of entries, but I get a class cast exception. Other criteria on same table work OK, so I'm sure most of the setup is good. Am I missing something really obvious? Is there an example available for querying by timestamp?

RE: newbie: using timestamp in criteria, compound primary key

2004-07-16 Thread jonathan . lister
oops, here is the output exception. Using OJB 1.0rc7 stable INFO: adding criteria greater than log_time 2004-07-14 12:26:52.578 16-Jul-2004 12:26:53 com.vaisala.ice.vmdbReport.view.IpmLogDAO getRecentActivity INFO: calling getCollectionByQuery 04/07/16 12:26:53 java.lang.ClassCastException

RE: newbie: using timestamp in criteria, compound primary key

2004-07-16 Thread jonathan . lister
excellent, works a treat now, many thanks ! -Original Message- From: Thomas Dudziak [mailto:[EMAIL PROTECTED] Sent: 16 July 2004 14:33 To: OJB Users List Subject: Re: newbie: using timestamp in criteria, compound primary key [EMAIL PROTECTED] wrote: very similar results using 1.0.0