-
Notifications
You must be signed in to change notification settings - Fork 379
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
Get rid of sqlite3NestedParse #3496
Comments
kshcherbatov
added a commit
that referenced
this issue
Jul 4, 2018
Now we manually generate AST structures to drop outdated stats from _sql_stat1 and _sql_stat4 spaces instead of starting sqlite3NestedParse. This function become totally useless and could be removed. Part of #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 4, 2018
As sqlite3NestedParse become totaly useless, let's remove unreacheble code and all mentioning. Resolves #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 4, 2018
Now we manually generate AST structures to drop outdated stats from _sql_stat1 and _sql_stat4 spaces instead of starting sqlite3NestedParse. This function become totally useless and could be removed. Part of #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 4, 2018
As sqlite3NestedParse become totaly useless, let's remove unreacheble code and all mentioning. Resolves #3496.
Gerold103
pushed a commit
that referenced
this issue
Jul 5, 2018
As sqlite3NestedParse become totaly useless, let's remove unreacheble code and all mentioning. Resolves #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 6, 2018
Now we manually generate AST structures to drop outdated stats from _sql_stat1 and _sql_stat4 spaces instead of starting sqlite3NestedParse. This function become totally useless and could be removed. Part of #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 6, 2018
As sqlite3NestedParse become totaly useless, let's remove unreacheble code and all mentioning. Resolves #3496.
Gerold103
pushed a commit
that referenced
this issue
Jul 9, 2018
Now we manually generate AST structures to drop outdated stats from _sql_stat1 and _sql_stat4 spaces instead of starting sqlite3NestedParse. This function become totally useless and could be removed. Part of #3496.
Gerold103
pushed a commit
that referenced
this issue
Jul 9, 2018
As sqlite3NestedParse become totaly useless, let's remove unreacheble code and all mentioning. Resolves #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 11, 2018
Now we manually generate AST structures to drop outdated stats from _sql_stat1 and _sql_stat4 spaces instead of starting sqlite3NestedParse. This function becomes totally useless and could be removed. Part of #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 11, 2018
As sqlite3NestedParse became totaly useless, let's remove unreacheble code and all mentioning. Resolves #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 11, 2018
Now we manually generate AST structures to drop outdated stats from _sql_stat1 and _sql_stat4 spaces instead of starting sqlite3NestedParse. This function becomes totally useless and could be removed. Part of #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 11, 2018
As sqlite3NestedParse became totaly useless, let's remove unreacheble code and all mentioning. Resolves #3496.
kshcherbatov
added a commit
that referenced
this issue
Jul 11, 2018
Now we manually generate AST structures to drop outdated stats from _sql_stat1 and _sql_stat4 spaces instead of starting sqlite3NestedParse. This function becomes totally useless and could be removed. Part of #3496.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This function was heavily used by legacy SQL code.
Now it is only used by
sql_clear_stat_spaces
.Rewrite it to directly emit byte code, which will clear corresponding
entries in stat[14] tables.
This issue need to be solved before #3319, there should be no recursion.
The text was updated successfully, but these errors were encountered: