Skip to content

3.5.3 – Not Yet Released

If you want to see all database schema changes for the 3.5.3 release, have a look at the migrations folder — specifically, all files containing __v3_5_3__ in their name.

Async Instead of Sync

This enhancement is related to performance. Simply put, the REST API core server can now handle many more concurrent connections. This is possible because its internal mechanics have changed: instead of handling connections and database requests synchronously, they are now handled asynchronously.

Home/Inbox DB Checks

This enhancement introduces the following database schema changes: users.home_folder_id and users.inbox_folder_id now have a "NOT NULL" database constraint. This means that, at the database level, it is guaranteed that a user will always have an existing home and inbox folder.

To make this technically possible, the nodes_user_id_fkey foreign key constraint on the nodes table was changed to be deferrable.

The purpose of this change is to prevent situations where a user is created without an associated home or inbox folder.

Length Limit on Users Columns

This is a security-related database schema change. The following columns of the users table now have upper length limits:

  • email: limited to 254 characters
  • password: limited to 255 characters
  • username: limited to 150 characters
  • first_name: limited to 100 characters
  • last_name: limited to 100 characters