You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/releases/0.2.1.md
+26-15
Original file line number
Diff line number
Diff line change
@@ -8,42 +8,50 @@ We also have a new form to allow users to submit suggestions and feedback about
8
8
9
9
_This page provides a comprehensive list of all changes since version [0.2.0](./0.2.0.md)._
10
10
11
-
<!-- ## Breaking changes -->
12
-
<!-- (This section lists any breaking changes to publicly exposed and documented machine interfaces to Mathesar such as the API or DB functions) -->
13
-
14
11
## Improvements
15
-
<!-- (Each feature within this section should have its own level-three heading) -->
16
12
17
13
### Database nicknames
18
14
19
-
[TODO]
15
+
Users can now assign nicknames to their configured databases, making it easier to identify and organize connections. Instead of relying on technical database names, users can set meaningful labels that will be used througout Mathesar.
16
+
17
+

18
+
19
+
20
+
This is especially useful when managing multiple databases with identical names, or when connecting to external services where database names are automated.
21
+
22
+

23
+
24
+
In addition to nickname support, all database connection values can now be edited.
25
+
20
26
21
27
[#4262](https://github.com/mathesar-foundation/mathesar/pull/4262"Frontend support for databases nicknames")
22
28
[#4244](https://github.com/mathesar-foundation/mathesar/pull/4244"Backend support for database nicknames")
23
29
[#4261](https://github.com/mathesar-foundation/mathesar/pull/4261"Allow DB name/host/port to be updated")
24
30
25
31
### In-app feedback
26
32
27
-
[TODO]
33
+
Users can now provide direct feedback within the app using a built-in feedback form. This simple input allows users to share thoughts, report issues, or suggest improvements without leaving the interface.
34
+
35
+

28
36
29
37
[#4241](https://github.com/mathesar-foundation/mathesar/pull/4241"Move feedback to app header, add mailing list link to home page")
30
38
31
39
### Column widths are persisted
32
40
33
-
[TODO]
41
+
Column widths in table views are now automatically saved, ensuring a consistent layout across sessions. Users no longer need to manually adjust column sizes every time they revisit a table, improving usability and efficiency when working with columns of varied lengths.
42
+
43
+

[#4248](https://github.com/mathesar-foundation/mathesar/pull/4248"Backend support to persist customized column widths")
37
47
38
48
### Drop schema contents when deleting
39
49
40
-
[TODO]
41
-
50
+
Mathesar now automatically drops all objects within a schema before deleting the schema itself, without relying on CASCADE. This ensures a safer and more controlled deletion process, preventing unintended removal of external dependencies while still allowing users to delete schemas that contain objects.
42
51
43
-
It's new behavior for Mathesar.
44
-
It's novel in the field, AFAIK. No other product (that I'm aware of) has the same combination of safety and convenience provided by this.
45
-
It warrants a bit more description, since the difference between this and CASCADE may surprise or interest a knowledgeable user, and may make some more confident when letting their users use Mathesar to access the DB.
52
+

46
53
54
+
This strikes a unique balance between safety and convenience, making it easier to manage schemas while reducing the risk of accidental data loss. It also provides greater confidence when granting database access to users, as deletions remain contained and predictable.
47
55
48
56
[#4251](https://github.com/mathesar-foundation/mathesar/pull/4251"Drop schema contents when deleting")
49
57
@@ -53,13 +61,17 @@ It warrants a bit more description, since the difference between this and CASCAD
53
61
54
62
See the [upgrading Postgres](#upgrading-postgres) section for instructions on safely upgrading your Postgres version.
55
63
56
-
New installs of Mathesar using our recommended [Docker Compose](../administration/install-via-docker-compose.md) installation will now use Postgres 17. Prior to 1.2.1 Mathesar installs configured via our docker compose file used version 13.
64
+
New installs of Mathesar using our recommended [Docker Compose](../administration/install-via-docker-compose.md) installation will now use Postgres 17. Prior to 1.2.1, Mathesar installs configured via our docker compose file used version 13.
57
65
58
66
59
67
[#4263](https://github.com/mathesar-foundation/mathesar/pull/4263"Upgrade docker compose to PG 17")
60
68
61
69
### Support connections without a database password
62
70
71
+
Mathesar now allows users to configure database connections without requiring a password. This provides greater flexibility for users relying on secure, passwordless authentication mechanisms while maintaining compatibility with a variety of database configurations.
72
+
73
+

74
+
63
75
[#4252](https://github.com/mathesar-foundation/mathesar/pull/4252"Partially support passwordless Database Roles")
64
76
[#4255](https://github.com/mathesar-foundation/mathesar/pull/4255"Copy suggestions for passwordless roles in Mathesar")
65
77
@@ -130,8 +142,7 @@ If you encounter issues or the upgrade fails:
130
142
docker compose up -d
131
143
```
132
144
133
-
For additional support, reach out to the Mathesar team via a [GitHub issue](https://github.com/mathesar-foundation/mathesar/issues/new/choose) or the [Matrix chat](https://wiki.mathesar.org/en/community/matrix).
134
-
145
+
For additional support, reach out to the Mathesar team via a [GitHub issue](https://github.com/mathesar-foundation/mathesar/issues/new/choose) or in the general channel of our [Matrix chat](https://wiki.mathesar.org/en/community/matrix).
0 commit comments