Search

Docly

WordPress database error: [Table 'wp_stemmadocs.wp_eazydocs_view_log' doesn't exist]
SELECT count FROM wp_eazydocs_view_log WHERE post_id = '5628' AND created_at = '2023-05-30' /* From [docs.stemma.ai/docs/stemma/frequently-asked-questions-faqs/what-effect-does-deprecating-a-table-have/] in [/nas/content/live/stemmadocs/wp-content/plugins/eazydocs/includes/Frontend/post-views.php:42] */

WordPress database error: [Table 'wp_stemmadocs.wp_eazydocs_view_log' doesn't exist]
SHOW FULL COLUMNS FROM `wp_eazydocs_view_log` /* From [docs.stemma.ai/docs/stemma/frequently-asked-questions-faqs/what-effect-does-deprecating-a-table-have/] in [/nas/content/live/stemmadocs/wp-content/plugins/eazydocs/includes/Frontend/post-views.php:47] */

What Effect Does Deprecating a Table Have?

Estimated reading: 1 minute

You can set the status of a table or dashboard as deprecated or intermediate. When you do so, that asset remains in the Stemma catalog, but is removed from default searches (you can change this by means of filters in Advanced Search).

When you deprecate an asset or change its status to intermediate, you should modify its description accordingly, and you should also be careful to message all users and owners of the asset (including users who might be using the asset indirectly, such as dashboard users of a table) to warn them about the change in status. This allows you to make sure you hear from all stakeholders before you remove or move the asset.

Articles