GenericAttribute + Customer_CustomerRole_Mapping tables in 3.4

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
9 years ago
I've just discovered the GenericAttribute table problem on a 2.8 site but see that it has now been resolved for guest users
(http://nopcommerce.codeplex.com/workitem/11306)

but it seems like it still doesn't clear when we delete a  regestered user

Also, I think we should have the ability to clear this table from admin to help declutter the database

I just reduced a database size from 184,910 mb   to    11,064 mb   by deleting the data in that table

======

Another issue - (forgive me if it's been resolved, i did look ! )



Customer_CustomerRole_Mapping   table

is very large even after deleting all guests and all but a handful of registered users

So,

I suggest that both deleting guests and deleting customers should clear data from

Customer_CustomerRole_Mapping   table
9 years ago
Hi Hayden,

It's by design. As you may know customers are really deleted. They are just marked as deleted. That's why these appropriate data also should not be deleted.
9 years ago
ok, got you - but what about the ability to clear the data from the genericAttributes table ?

would this be such a bad idea to allow some housekeeping ?
9 years ago
All data from "GenericAttribute" is already deleted when guests are deleted (marked as deleted) in the "DeleteGuestCustomers" method of the "CustomerService" class.

But it should not be done for registered customers which are deleted. Furthermore, registered customer records are deleted very rarely (hence it won't give any real enhancement). You'll have to customize the solution in order to archive it.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.