Skip to content

Resolve "Created by field type"

Davide Silvestri requested to merge 624-created-by-field-type into develop

The main goal of the MR is to add "created_by" column to generated tables and set this column when rows are created. Export/import and other features are also supported.

Acceptance criteria/test cases

  • Older tables will get a new created_by column upon opening a view or when a field is created
  • New tables get a new created_by column automatically from the beginning
  • The rows that are created by "new table" operation are automatically set to be created by the person creating the table
  • The rows that are created by "from template" operation are automatically set to be created by NULL, but the column will exist from the beginning
  • Submitting forms will save the logged user as created_by for the new rows, and use NULL for anonymous submissions
  • Create row operations set the value when creating rows (create row, create rows)
  • Updating rows doesn't result in change in created_by
  • Moving (reordering) rows doesn't result in change in created_by
  • Deleting (trashing rows) doesn't result in change in created_by
  • When a user is removed from workspace tables will keep the user reference in the row
  • When a user is deleted the value will be lost (foreign key)
  • Importing rows to a table will assign created_by to the person who did the import
  • Workspace import/export preserves created_by if user is in the new workspace, otherwise sets to NULL
  • Duplicating databases/tables preserve original created_by in rows
  • Snapshots, and restored databases and tables from snapshots preserve created_by references
  • All fields Baserow template now includes also the last_modified_by and the created_by fields
  • It's possible to filter by created_by user
  • It's possible to sort by created_by user
  • It's possible to search by first_name (the visible user name) in a created_by field

Merge Request Checklist

  • changelog.md has been updated if required.
  • New/updated Premium/Enterprise features are separated correctly in the premium or enterprise folder
  • The latest Chrome and Firefox have been used to test any new frontend features
  • Documentation has been updated
  • Quality Standards are met
  • Performance: tables are still fast with 100k+ rows, 100+ field tables
  • The redoc API pages have been updated for any REST API changes
  • Our custom API docs are updated for changes to endpoints accessed via api tokens
  • The UI/UX has been updated following UI Style Guide

Closes #624 (closed)

Edited by Davide Silvestri

Merge request reports