Skip to content
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.

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

SQLite RevEng: Reverse engineer index filters #8800

Open
Tracked by #22950 ...
bricelam opened this issue Jun 9, 2017 · 0 comments
Open
Tracked by #22950 ...

SQLite RevEng: Reverse engineer index filters #8800

bricelam opened this issue Jun 9, 2017 · 0 comments

Comments

@bricelam
Copy link
Contributor

bricelam commented Jun 9, 2017

The built-in metadata APIs only tell you that it is a partial index, not what the filter is. We may have to parse the CREATE INDEX statement, but we should be able to extract the WHERE clause and put it in the HasFilter call.

@ajcvickers ajcvickers added this to the Backlog milestone Jun 12, 2017
@ajcvickers ajcvickers added the help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. label Jun 12, 2017
@divega divega added good first issue This issue should be relatively straightforward to fix. help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. and removed help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. good first issue This issue should be relatively straightforward to fix. labels May 31, 2019
@ajcvickers ajcvickers added good first issue This issue should be relatively straightforward to fix. and removed help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. labels Aug 5, 2019
@bricelam bricelam removed the good first issue This issue should be relatively straightforward to fix. label Nov 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants