Add WP_SQLITE_DB_NAME constant to take precedence over DB_NAME #261
Conversation
This file contains hidden or 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
Author
|
@JanJakes , what do you think about using this constant to override the DB_NAME? |
sejas
commented
Oct 3, 2025
| * TODO: For version 3.0, enforce the DB_NAME constant and remove the fallback. | ||
| */ | ||
| if ( defined( 'DB_NAME' ) && '' !== DB_NAME ) { | ||
| if ( defined( 'WP_SQLITE_DB_NAME' ) && '' !== WP_SQLITE_DB_NAME ) { |
Author
There was a problem hiding this comment.
I added the prefix WP_SQLITE_ to be consistent with other constants required by this plugin, such as WP_SQLITE_AST_DRIVER.
sejas
changed the title
1 task
Author
|
epeicher
approved these changes
Oct 7, 2025
epeicher
left a comment
epeicher
left a comment
There was a problem hiding this comment.
Thanks @sejas for improving this! I’ve tested it, and can confirm that after breaking the connection, applying these changes, and adding the new constant, the site works again.
This LGTM, so I’m accepting the PR, but leaving it to you or someone from the team to decide whether to merge it.
| Database name incorrect | Adding the constant | Refreshing the site |
|---|---|---|
 |
 |
 |
Merged
Member
|
Closing this in favor of #266. |
JanJakes
added a commit
that referenced
this pull request
Oct 15, 2025
This PR replaces #262. It is a simpler solution to the same problem: When a table reference targets an information schema table, we replace it with a subquery, injecting the configured database name dynamically: ```sql -- The following query: SELECT *, t.*, t.table_schema FROM information_schema.tables t -- Will be translated to: SELECT *, t.*, t.table_schema FROM ( SELECT `TABLE_CATALOG`, IIF(`TABLE_SCHEMA` = 'information_schema', `TABLE_SCHEMA`, 'database_name') AS `TABLE_SCHEMA`, `TABLE_NAME`, ... FROM _wp_sqlite_mysql_information_schema_tables AS tables ) t ``` The same logic will be applied to table references in JOIN clauses as well. --- With the new SQLite driver, we keep running into issues with missing and incorrect database name values (#197, #203, #226, #260, #261, and other issues). Thinking through this further, I came to the conclusion that to provide maximum flexibility and portability, it would be best to provide an API in the shape of: _"Mount `my-sqlite-file.sqlite` as `my-db-name`."_ Even if we consider adding multi-database support one day, it would still be great to allow mounting additional SQLite files under dynamic database names. I don't see any downsides to doing this, except maybe that we'll have to choose some database name in some scenarios, such as in database admin tools. However, in these cases we can use a reasonable default or the file name. This is a WIP pull request demonstrating the simplest approach. For it to be merged, I only need to resolve how the existing database name values should be treated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Because filters actually don’t work in db.php, I suggest removing the
wp_sqlite_default_db_namefilter and introducing a new constantWP_SQLITE_DB_NAMEto take precedence over DB_NAME.Error establishing a database connectiondefine( 'WP_SQLITE_DB_NAME', 'database_name_here' );Credit to @wojtekn for the code. I just removed the filter as it seemed misleading.