Not qualified columns when projection is null
PomepuyN opened this issue · 1 comments
PomepuyN commented
With the 1.8.1 version of the lib, there are two bugs:
- With a null projection, the index returned by
getCachedColumnIndexOrThrow
ofAbstractCursor
is not qualified and therefor is the first one found that have the colName - In the
XXXProvider.getQueryParams
method, thequalifyAmbiguousColumns
should be called on all joined tables
BoD commented
I believe this issue is no longer relevant with the 1.8.1 version that I just released.