Hi Clinton, Thanks for the info.
> This is just one reason why I always recommend using JavaBeans > for 99% of your work. Maps are inconsistent, unpredictable, > not typesafe and slow. I agree. Typesafety is a major issue when dealing with databases. If you're not careful, you end up comparing numerics with strings and vice-versa... Our use of Maps is very limited. We build all our complex queries based on JavaBean properties (especially for typesafety). These queries usually need to be called twice: one for counting the number of results, the other to get the actual results. Our view is that the call to a statement as a "count query" should not be part of the search criteria. To solve this we use Maps in which we put the search criteria (JavaBean) and another property that states whether the statement should build a "count query" or not. This other property is only present when the call is a "count query", so the test is made using the isPropertyAvailable tag. We can easily modify our statements to use another tag for testing this property. I'm wondering, what's your take on the isPropertyAvailable tag since it's no longer useful? Will it be deprecated, removed or adjusted? Thanks a bunch, Philippe -----Original Message----- From: Clinton Begin [mailto:[EMAIL PROTECTED] Sent: December 15, 2004 9:48 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Information about changelog Ewww.....yes. This was causing inconsistent behaviour between parameter maps and result maps and it was therefore necessary to simply always return true. Basically a Map doesn't have properties and you can always set any value. This is just one reason why I always recommend using JavaBeans for 99% of your work. Maps are inconsistent, unpredictable, not typesafe and slow. Cheers, Clinton On Tue, 14 Dec 2004 23:41:24 -0500, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Can someone provide me with information regarding this entry in the > 2.0.8 > changelog: > > o Probes now always return true for hasReadable/hasWriteable property > checks. > > Is there a thread about this? Or can someone brief me on it? > > I'm looking to upgrade my version of iBatis and I think this > modification has possibly changed the behaviour of the > isPropertyAvailable tag. We use this tag on Map instances as a > parameterClass and it doesn't seem to behave like it does in 2.0.7. > > I'd like to dig further, so I was wondering what the intent of this > modification was... > > Regards, > Philippe >
