[rt-users] RT 3.4.2 custom fields defaulting to value '1'

[Jason Parsons]

On Aug 4, 2005, at 9:23 AM, David Glasser wrote:

> This bug should be fixed in the forthcoming RT 3.4.3.  Try 3.4.3  
> release candidate 2 and let us know if this bug still exists.

3.4.3 did resolve this problem.

Is it safe to DELETE FROM ObjectCustomFieldValues the bogus entries?   
A quick review seems to suggest that it would be safe to selectively  
drop rows from ObjectCustomFieldValues, but it would be nice to know  
if this will create any inconsistencies.

Thank you.
   - Jason Parsons