Hi Sergey,
I have an idea of what the mentioned table is about, but it seems it could use some "housekeeping"?
As I'm playing around with things - e.g. by creating users, orders, subscriptions, then deleting them again (in the backend), I gladly notice that no matter if I delete subscriptions or Joomla users, the Emerald tables stay generally nicely tidy. Except, this table keeps only growing, its rows are not getting deleted once anything else is. Additionally, the table has no "unique column" (primary key?), so even clearing it in phpMyAdmin takes a little extra effort.
Right now not a problem, but I'm fearing for the long-term future: there will be deletions made by the client, of course, and with >15k subscriptions to start with, this table might grow out of proportion and manual housekeeping would get ugly, should it ever be required.
What do you say? Thanks in advance for a note on this.
Question
Announcement
Conversation
Idea
Praise
Problem
Reviewed
Open
Hi Sergey,
I have an idea of what the mentioned table is about, but it seems it could use some "housekeeping"?
As I'm playing around with things - e.g. by creating users, orders, subscriptions, then deleting them again (in the backend), I gladly notice that no matter if I delete subscriptions or Joomla users, the Emerald tables stay generally nicely tidy. Except, this table keeps only growing, its rows are not getting deleted once anything else is. Additionally, the table has no "unique column" (primary key?), so even clearing it in phpMyAdmin takes a little extra effort.
Right now not a problem, but I'm fearing for the long-term future: there will be deletions made by the client, of course, and with >15k subscriptions to start with, this table might grow out of proportion and manual housekeeping would get ugly, should it ever be required.
What do you say? Thanks in advance for a note on this.