Re: OJB 1.0.5 release candidate 1 (unofficial)

2008-01-29 Thread Armin Waibel
Hi Ilkka, Ilkka Priha wrote: Thanks Armin! Seems to work great with our app (MySQL-NT). Thanks for testing! The only found inconsistency with the previous version was that the default CopyStrategyImpl in ObjectCacheTwoLevelImpl is now final. We apply dynamic persistent Variables, which

BUGREPORT : OJB 1.0.5 release candidate 1

2008-01-29 Thread Janssen, Roger
Hi, Finally migrating away from 1.0rc6 to 1.0.5rc1 . :) Started migration our persistence layer around OJB, think a found a bug. When we create a reportquery and want to execute a count first, we get a ClassCastException. Caused by: java.lang.ClassCastException:

BUGREPORT : OJB 1.0.5 release candidate 1 (unofficial)

2008-01-29 Thread Janssen, Roger
Hi, Like a reported earlier, something goes wrong with count queries. When I hack some code in BrokerHelper, to get around the first bug (I don't know if what I do is correct, but I am trying): private Query getReportQueryByCriteriaCount(ReportQueryByCriteria aQuery) { Query

Mapping for type BIT broke afer upgrade from 1.0.1 to 1.0.4

2008-01-29 Thread Oliver Seimel
Hi, we migrated from ojb 1.0.1 to 1.0.4 DB is Postgres. But I think, that the problem is independent of the DB. We use the type BIT(1) for boolean values, so a mapping looks like this: field-descriptor name=emailNotice column=emailnotice jdbc-type=BIT / With version 1.0.1 the

Re: BUGREPORT : OJB 1.0.5 release candidate 1 (unofficial)

2008-01-29 Thread Armin Waibel
Hi Roger, thanks for testing the upcoming 1.0.5 release. Janssen, Roger wrote: Hi, Like a reported earlier, something goes wrong with count queries. I can reproduce this bug (thanks for detailed description). When I hack some code in BrokerHelper, to get around the first bug (I don't

AW: Mapping for type BIT broke afer upgrade from 1.0.1 to 1.0.4

2008-01-29 Thread Oliver Seimel
Hi Armin, Oliver Seimel wrote: Hi, we migrated from ojb 1.0.1 to 1.0.4 DB is Postgres. But I think, that the problem is independent of the DB. We use the type BIT(1) for boolean values, so a mapping looks like this: field-descriptor name=emailNotice

Re: Mapping for type BIT broke afer upgrade from 1.0.1 to 1.0.4

2008-01-29 Thread Armin Waibel
Hi Oliver, Oliver Seimel wrote: Hi, we migrated from ojb 1.0.1 to 1.0.4 DB is Postgres. But I think, that the problem is independent of the DB. We use the type BIT(1) for boolean values, so a mapping looks like this: field-descriptor name=emailNotice column=emailnotice