-
Notifications
You must be signed in to change notification settings - Fork 59
Remove legacy SQLite driver #358
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
Changes from all commits
2ee298a
522724d
1bc31c3
9263d77
ecaa3dd
1437789
dd88684
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,8 +15,6 @@ SQLite integration plugin by the WordPress Team. | |
|
|
||
| The SQLite plugin is a community, feature plugin. The intent is to allow testing an SQLite integration with WordPress and gather feedback, with the goal of eventually landing it in WordPress core. | ||
|
|
||
| This feature plugin includes code from the PHPMyAdmin project (specifically parts of the PHPMyAdmin/sql-parser library), licensed under the GPL v2 or later. More info on the PHPMyAdmin/sql-parser library can be found on [GitHub](https://github.com/phpmyadmin/sql-parser). | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a general correction, not related to this PR, right?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's related, actually. The legacy driver used a simple lexer/parser extracted from PHPMyAdmin. The new driver doesn't use any of this.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see. |
||
|
|
||
| == Frequently Asked Questions == | ||
|
|
||
| = What is the purpose of this plugin? = | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice for this to still say (AST) as suffix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, the problem is I think most users won't know what that means. It made some sense when it was a feature flag, but otherwise, I'd say it's an implementation detail of the parser.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, it's an implementation detail. Users who were not using AST would now be using it in future with the newer version of plugin as soon as they update, right? So with that context in mind and personally, as a user I would like to see it.
But feel free to choose what you think is best.