How are Images / files handled

[tomt92]

Hi All,

I didn’t see an answer to this question, and I was wondering how assets (images / files) are handled. From what I have seen they are stored in a separate backend system — Seafile, but in not sure the relationship between that store and the Base files. Specifically I’m wondering about the following scenario:

— I create a base and a table in that base with an image column. Later I create a new base and import the table from the first base with all of its data. If I delete the first base will the assets be removed at the 30-day mark when the trash is emptied…

More specifically – does the copying the table copy the assets? Or are the assets linked to both tables? Is the backend aware of all these links and only removes the asset if all links are removed?

If I go into the new base and the asset manager I can only see assets that I uploaded to that base.

[Soonimproveduser]

There are file and picture columnes available in SeaTable

[daniel.pan]

@tomt92

Seafile, but in not sure the relationship between that store and the Base files.

Assets are stored in SeaTable’s seaf-server component, not a separate Seafile application.

When you copy a base or import a table from another base, the assets are copied too. So deleting original base will not delete the copied assets.

[rdb]

@tomt92

More specifically – does the copying the table copy the assets? Or are the assets linked to both tables? Is the backend aware of all these links and only removes the asset if all links are removed?

The assets are copied when you import a single table from another base as well as when you duplicate a base.

If I go into the new base and the asset manager I can only see assets that I uploaded to that base.

In keeping with the above, when I import a table in another base, I see all assets that were saved in the imported table. When I duplicate a base, I see all assets that existed in the duplicated base.