Skip to content

Mathesar 0.1.4


Mathesar 0.1.4 focuses on improving the installation and setup experience.

This page provides a comprehensive list of all changes in the release.

Upgrading to 0.1.4

See our guide on upgrading Mathesar to 0.1.4.

New Features

UI for configuring database connections

Now you can add, edit, and delete connections to multiple databases from within Mathesar’s UI. Previously this was only possible via editing text-based configuration.



#3170 #3223 #3299 #3309 #3319 #3326 #3341 #3348 #3349 #3352 #3354 #3356 #3368 #3377 #3387

Sample data loader

When adding a new database connection, you can choose to load sample data into that database. Sample data will be contained within specific schemas and may be useful to help new users play with Mathesar’s features.



PostgreSQL column COMMENTs

PostgreSQL COMMENT values on columns are now exposed via a read/write “description” field within Mathesar. This feature was previously available for schemas and tables and is now available for columns too.


#3186 #3219

Text-only imports

When importing CSV data, Mathesar now gives you the option to use TEXT as the database type for all columns. This choice speeds up the import for larger data sets by skipping the process of guessing colum types.



We are still considering additional ways to improve performance when importing — especially for data sets with lots of columns.

Reduced database privilege installations

Mathesar can now be installed as long as the database role used during the installation has at least CONNECT and CREATE privileges on the database targeted by the installation. If you want to create a new database for Mathesar’s use, the installation will (naturally) require a role with the CREATEDB privilege.


Unified Mathesar Docker image

The published Mathesar Docker image now contains a PostgreSQL server. This is used to provide a database backend in cases where Mathesar is started via Docker without being configured to connect to any other database.

#3121 #3212

Metadata storage within SQLite

We’ve added experimental SQLite support for the storage of Mathesar metadata. This will allow brave (or foolish) users to run Mathesar with this lighter-weight DB when installing from scratch on Linux.

#3203 #3225 #2778

Improved PostgreSQL compatibility

Mathesar now officially supports, and is tested against, Postgres versions 13, 14, and 15. It’s also possible (but not yet recommended) to run Mathesar using Postgres 16.


Easier modification of sorting precedence

When you have multiple sorting conditions applied to a table, you can now rearrange them via drag and drop to adjust the precedence of the sorting conditions.



Cell values displayed within sidebar

The table sidebar features a new “Cell” tab to show the content of cells, simplifying the process of viewing large text cells.



  • We made significant progress towards internationalizing Mathesar’s user interface. We expect to our next release to offer users the ability to toggle between English and Japanese. Subsequent releases will continue to add additional languages.

    #3102 #3103 #3104 #3302 #3321 #3337 #3340 #3350 #3389

  • We began some work that will help us eventually distribute Mathesar via a Debian .deb package. Some additional work remains but we hope to introduce this installation method in a future version.

    #3189 #3225

  • We implemented the backend side of a new feature to import Excel and JSON files through Mathesar’s import UI. More work still remains to implement the frontend side of this feature.

    #3083 #3195 #3132

  • We took some baby steps towards building a system to automatically generate human-readable documentation for all our API endpoints. Significant work still remains.

    #3271 #3146


  • We improved and updated our documentation for installing and updating Mathesar. (#3227)

Bug fixes

  • Tables having CHECK constraints are now usable within Mathesar. (#3243)
  • Records can now be inserted into tables without primary keys. (#3252)
  • We fixed inconsistent state when selecting a different column while editing a column’s name. (#3219)
  • URL cells now retain their focus after a contained hyperlink is clicked. (#3012)
  • Searching for a record via a partially-entered date string no longer gives an error. (#3343)
  • The Database Page now shows loading and error indicators. (#3351)
  • The Schema Page now displays more detailed information about errors encountered when loading tables and explorations. (#3323)
  • Exclusion constraint violations now produce more helpful error messages. (#3200)
  • Files with missing or duplicate id values can now be imported without error. (#3155)
  • The record selector can now be closed by clicking on the overlay outside its modal. (#3220)
  • Help text for foreign key column data types is now more accurate. (#3260)
  • Users of Mathesar’s public demo site will no longer see database connections listed for other demo users. (#3129)
  • More UI elements have visually distinctive focus states. (#3313)
  • Date formatting is applied to arrays of date values. (#3325)
  • On the record page, values within foreign key columns can now be set to NULL more intuitively. (#3310)
  • A visual layout overflow bug on the record page is fixed. (#3303)
  • Foreign keys referencing non-primary-key columns now display properly. (#3239)


  • We made our CI pipeline more robust. (#3254)
  • We made some updates to our workflows and developer documentation to support improvements to our issue labeling scheme. (#3338 #3298 #3280 #3336)
  • We made some routine upgrades to dependencies and small adjustments to development tooling. (#3214 #3353 #3334 #3201 #3295 #3156 #3234 #3229 #3317)
  • We addressed regressions from work during this release. (#3197)
  • We improved error handling by preventing storing non-positive IDs for certain objects.(#3177)
  • We clarified the API behavior by specifying JSON-only requests (#3090)
  • We improved testing against DB objects with long names (#3140)
  • We updated our org name to reflect a change from “Center of Complex Interventions” to “Mathesar Foundation”. (#3312)
  • We made some improvements to our developer documentation. (#3300 #3210 #3279)
  • We improved our process for generating release notes. (#3427)
  • We resolved some merge conflicts after finalizing our previous release. (#3190)