Create DBD::SQLite::GetInfo with a more verbose set of data #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Awesome! Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I figured it was about time DBD::SQLite got its own GetInfo module with a complete set of data. After all, other drivers like MySQL, Oracle, and Pg already have them.
I know some use this for ODBC connectivity, and I've factored that into some of the values. But, this is also really useful to query certain values to use in a RDBMS-agnostic way. Such as making sure the LIKE escape character is \ with SQL_SEARCH_PATTERN_ESCAPE, or figuring out the maximum table name with SQL_MAX_TABLE_NAME_LEN.