See my reply to Dragan. Most of my issues are with the class interface oddities and the fact that it's framework unfriendly if you're building on top of it. If you're just plugging it into an application as is - I suppose it's OK if you can get past the arkane syntax, but if you're building a framework it's not a good fit because it by itself wants to be a data framework :-).

It's a preference but CA just never made sense to the way I've always worked with data.

+++ Rick ---

>I am with Dragan that it provides eventhooks, which can be quit useful, starting with logging.
>
>If you are just talking about somewhat heavy method signature, fully agree,
>perhaps also about somewhat redundant/talkative needs for setup in the properties -
>could have been handled better/more automated or preabstracted with setters.
>
>Do you have another gripe I did not stumble upon ?
>
>curious
>
>thomas
>
>
>>Sorry I meant CursorAdapter. It's one of the most awkward abstraction APIs I've ever seen for doing data access :-) The functionality it provides is decent but the way code has to interact with it is ugly at best IMHO. I never used it beyond playing with it for that reason.
>>
>>To me the straight forward approach of SQL Passthrough is simply more transparent and allows you full control over the entire data access process...
>>
>>+++ Rick ---
>>