New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not qualified columns when projection is null #40

Closed

PomepuyN opened this issue Oct 20, 2014 · 1 comment

Contributor

PomepuyN commented Oct 20, 2014

With the 1.8.1 version of the lib, there are two bugs:

With a null projection, the index returned by getCachedColumnIndexOrThrow of AbstractCursor is not qualified and therefor is the first one found that have the colName
In the XXXProvider.getQueryParams method, the qualifyAmbiguousColumns should be called on all joined tables

The text was updated successfully, but these errors were encountered:

PomepuyN changed the title ~~Not qualified columns when prjection is null~~ Not qualified columns when projection is null

BoD added a commit that referenced this issue


          Fixes 2nd point of issue #40.

Owner

BoD commented Nov 11, 2014

I believe this issue is no longer relevant with the 1.8.1 version that I just released.

BoD closed this as completed

frigus02 mentioned this issue

Not qualified columns when projection is null (relevant again) #86

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment