Skip to content
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

sqlite3 connection uses old DB file path when connection properties change #598

Open
eug3nix opened this issue Jan 31, 2025 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@eug3nix
Copy link
Collaborator

eug3nix commented Jan 31, 2025

Steps to reproduce
0. Create SQLite3 connection to an existing database A (lets call it databaseA.db)

  1. Connect to this database, inspect database contents, close the connection
  2. Edit connection, change the DB file path (lets call it databaseB.db)
  3. Connect to the database, inspect database contents.

Expected:
databaseB contents should be shown

Observed:
databaseA contents are shown

Additional details:
changeActiveDatabase with the old db path may be causing this, look in the store, maybe erase last_used_database when connection manager makes API call to update it.

@eug3nix eug3nix added the bug Something isn't working label Jan 31, 2025
@plucik plucik self-assigned this Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants