Multi-value field does not refresh from database changes (was: How to reload a table in the UI)

[christophberger]

I connected DBeaver to the database and modified a few rows. In the Teable UI, the old data keeps showing.

How can I refresh/reload the table to fetch the changes from the database?

---

Update: The tables seem to reload, but I changed some tags (a multi-select field), and the changes don't show in the UI. If I change tags in the UI instead, the change appears properly in the database.

So the behavior seems to be specific to multi-select fields.

---

Update 2: The table is imported from CSV. The tags column is of DB type JSONB and of cellValueType string.

[tea-artist]

Teable is currently designed to control the entire database. some functionality may not work correctly if you modify the database directly instead of through teable API or UI

https://help.teable.io/developer/database-connection#direct-database-writing

[christophberger]

Thanks for the explanation. Do I understand this correctly: A small change in the column of a record breaks the logic?

Background:
I imported a CSV with multiple tags in one column. Naturally, the CSV encloses the comma-separated tags in quotes, to avoid messing with the CSV commas. So, in the database, the tags column (configured in the UI as a multi-select field) contains the tags as a single value:

["abstraction, leaky_abstraction, software_development"]

Teable takes this as a single tag:

Now, when I change the database column to the correct format in DBeaver...

["abstraction", "leaky_abstraction", "software_development"]

...then the UI shows nothing:

I know that I should fix the CSV before importing, but this is not the point here. The point is that I cannot alter column values directly without breaking the UI.

Is this a bug? Shall I open an issue?
Or is this expected behavior, based on your advice that the database must not be altered?

If the latter applies, I cannot use Teable for my use case, which requires that other apps can interact with the database directly. (Which works perfectly fine with NocoDB, by the way.)

[tea-artist]

Yes, the database must not be altered, currently, any problems caused by direct modifications to the database will not be supported.
In terms of implementation, this is feasible, but many details need to be worked out to support direct modification of the database.

(by the way, thanks for providing the detailed scene, which will provide a good reference for our subsequent design

[tea-artist]

After our discussion, we feel that this function is of great practical value, and we decided to implement this capability in a future release, thanks for the feedback!