SoilentRed
Caaan do!
All,
I don't know how this could have occurred, so maybe the correlation is not necessarily the cause, but on Friday evening, I ran my GitHub update of Fabrik and everything seemed to have gone over smoothly. I have a backup from about 6 hours before I ran the update, and I have a backup immediately after the update.
I have a table, 06_member_subscription, that held 117,308 rows (18.3 MiB) before the update, and 34,861 rows (5.4 MiB) after the update.
Have you ever heard of this happening due to an update? is that possible? I'm glad I have the dataset, but I'm absolutely lost wondering how this possibly could have happened. Any thoughts?
I don't know how this could have occurred, so maybe the correlation is not necessarily the cause, but on Friday evening, I ran my GitHub update of Fabrik and everything seemed to have gone over smoothly. I have a backup from about 6 hours before I ran the update, and I have a backup immediately after the update.
I have a table, 06_member_subscription, that held 117,308 rows (18.3 MiB) before the update, and 34,861 rows (5.4 MiB) after the update.
Have you ever heard of this happening due to an update? is that possible? I'm glad I have the dataset, but I'm absolutely lost wondering how this possibly could have happened. Any thoughts?
