Skip to content

research:nocodb

Johannes Lötzsch edited this page Mar 24, 2023 · 5 revisions

Exemplary features

+ (very) good usability

+ many users + developers

+ FOSS

  • AGPL

+ easy to setup

+ good codebase

+ typescript

+ readable model

  • vue
  • monorepo

+ well documented

- but could be more documentation for developers

+ powerful API

+ REST (including Swagger)

  • Graphql is promised, but not documented

+ Webhooks

+ links between tables

supporting several sql databases

import/export (with limitations)

json, csv, xlsx

enough features for many usecases

most important primitive datatypes

Limitations

- No end-to-end-encryption

- Permissions can't be limited per column (?)

- No subscriptions / MQ

form views are very limited

inspiring "wizard"

  • views are defined after defining column types of sheet

+ quite good usability of "wizard" via drag&drop

- changing type is not possible while editing form view

- forms are barely customizable

- only one renderer per datatype

- no concept of grouping (nor nesting)

- no customizable styles

- not translatable forms

- limited datatypes

- effort to extend them (due to design decisions)

- no "external" schema

- types are flat (primitives only)

- types are hard coding "UI-Type" to db datatypes

- db schema needs be updated for new "UI-Types" and views

- no support for configuration tables (first class citizens)

- no translations

- enums can not be feed from tables

- limited views

- no nested renderers/views