How do you handle schema changes like adding columns or changing the type of columns? Is the schema fixed at design time by a database admin, or can the end-user add/remove columns, create tables, and introduce relationships?
That is what I want to share. When users create fields in the visible table, it directly creates columns in the corresponding Postgres table. There's a mapping between the fields on the UI and the physical columns. At the same time, relationships are a major highlight; the "link field" of the Teable will create logical foreign keys or junction tables between physical tables to maintain the relationship.