Skip to content

Commit

Permalink
Clarify effects of upgrading
Browse files Browse the repository at this point in the history
  • Loading branch information
seancolsen committed Jan 24, 2025
1 parent 11a2891 commit 51435f4
Showing 1 changed file with 9 additions and 1 deletion.
10 changes: 9 additions & 1 deletion docs/docs/releases/0.2.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -454,7 +454,15 @@ The following PRs represent work done to reduce technical debt, update dependenc

## Upgrading to 0.2.0 {:#upgrading}

We do not fully support upgrading from previous versions to `0.2.0`. In particular, you will lose any Explorations and User accounts (e.g., usernames and passwords) you created in Mathesar during the process. Furthermore, manual steps are required.
Upgrading to version 0.2.0 will:

- **Remove** out your [user](../user-guide/users.md) accounts, passwords, [explorations](../user-guide/data-explorer.md), and [metadata](../user-guide/metadata.md). You will need to recreate these after the upgrade.
- **Keep** your databases and the data within them.

!!! question "Should I upgrade or reinstall?"
- If any of your connected databases reside inside Mathesar's internal database server, then you will need to perform the upgrade steps below or export your data (e.g. via `pg_dump`) and reinstall Mathesar.

- If all of your connected databases reside in PostgreSQL servers _outside_ the Mathesar's Docker containers, then the quickest way for you to get to 0.2.0 is to reinstall Mathesar and reconnect your databases.

### For installations using Docker Compose

Expand Down

0 comments on commit 51435f4

Please sign in to comment.