GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — opt: support new features in SQLite by bajinsheng · Pull Request #654 · sqlancer/sqlancer Conversation
|
| public boolean executeQuery = true; | ||
|
|
||
| @Parameter(names = { | ||
| "--max-tables" }, description = "The maximum number of tables/virtual tables/ rtree tables/ views that can be created") |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Could we use --max-num-tables here and --max-num-indexes below, to match the naming convention of other option classes (see below)?
| @Parameter(names = "--max-num-views", description = "The maximum number of views that can be generated for a database", arity = 1) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Fixed
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
|
||
| @Parameter(names = { | ||
| "--max-tables" }, description = "The maximum number of tables/virtual tables/ rtree tables/ views that can be created") | ||
| public int maxTable = 10; |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
perhaps maxNumTables?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| public int maxTable = 10; | ||
|
|
||
| @Parameter(names = { "--max-index" }, description = "The maximum number of indexes that can be created") | ||
| public int maxIndex = 20; |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Perhaps maxNumIndexes?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| REINDEX(SQLite3ReindexGenerator::executeReindex), // | ||
| ANALYZE(SQLite3AnalyzeGenerator::generateAnalyze), // | ||
| DELETE(SQLite3DeleteGenerator::deleteContent), // | ||
| PRAGMA(SQLite3PragmaGenerator::insertPragma), // 0 |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Not sure why we are numbering the actions here?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I number these actions for debugging. The enumeration variable only includes index information in execution, and these numbers help me to quickly locate which action is selected and executed.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sorry, something went wrong.
There was an error while loading. Please reload this page.
* opt: support maximum number of table/index * opt: support explain interface
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.