residue left in DB after field removal

7.0.3

After a custom profile field has been deleted Fields are left  in table sys_localization_strings and sys_localization_keys . This will gunk up the db. For instance. I added a profile field with 50 options. I then deleted the field but was still left with all they keys and Strings!

You really should add a field to keys and strings tables to identify the sys_profile_fields that the keys and strings are associated with  , then remove everything based on the sys_profile_fields identifier. Then junk wont be left over in keys and strings.....

 

Just my opinion. Im probably going to code this myself just to keep my own db clean.....

Giving it another shot......
Quote · 18 Nov 2010

i think that is a grand idea. i think that when x is deleted, it should clean all of x's trash.

 

maybe this will be addressed in upcoming releases......

 

When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support
Quote · 18 Nov 2010
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.