Restore a collection

[vogtjob]

If a collection has been deleted through Application Management -> Collections --> Delete Collection, is there a method to restore/undelete the collection?

[csmig]

Yes, but that capability is not yet exposed via an API endpoint. A feature that is likely to introduce it can be tracked at #1386.

However, it is possible today to restore a "deleted" Collection by directly modifying the backend database. In the collection table, discover the collectionId of the Collection to be restored and issue this query:

UPDATE collection SET state = 'enabled' WHERE collectionId = ?

where ? is the collectionId. This will not update the stateDate or stateUserId columns, but if that is important for you they can be modified with a similar query.

This query works because when a Collection is "deleted" via API the Collection is simply marked as disabled. That approach has the advantage of not invoking a potentially very expensive purging of millions of records. But it can lead to database bloat, which is the prime motivation behind our development of #1386.

[vogtjob]

Thank you. That is exactly what I needed to know!

…

On Tue, Feb 11, 2025 at 6:23 AM csmig ***@***.***> wrote: Yes, but that capability is not yet exposed via an API endpoint. A feature that is likely to introduce it can be tracked at #1386 <#1386>. However, it is possible today to restore a "deleted" Collection by directly modifying the backend database. In the collection table, discover the collectionId of the Collection to be restored and issue this query: UPDATE collection SET state = 'enabled' WHERE collectionId = ? where ? is the collectionId. This will not update the stateDate or stateUserId columns, but if that is important for you they can be modified with a similar query. This query works because when a Collection is "deleted" via API the Collection it is simply marked as disabled. That approach has the advantage of not invoking a potentially very expensive purging of millions of records. But it can lead to database bloat, which is the prime motivation behind our development of #1386 <#1386>. — Reply to this email directly, view it on GitHub <#1518 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4P6FRQUIJ3HIQHGARHXRJD2PHMS3AVCNFSM6AAAAABW2UUNR2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJTHE2DKMA> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>