View Issue Details

IDProjectCategoryView StatusLast Update
0000404SymmetricDSBugpublic2011-01-25 21:30
ReporterAssigned Tochenson  
Status closedResolutionfixed 
Product Version2.1.2 
Target Version2.2.0Fixed in Version2.2.0 
Summary0000404: Should always check for duplicate trigger names, not just when the trigger name is > max length
Description"We have ran into an issue where Symmetric DS creates 2 triggers with the same name (sym_on_i_for_sm_mcpdb_prmry). The underlying table names are ""sm"" and ""asm"". When I looked at the getTriggerName method, it bypasses the code to ensure the triggername is unique when the length is < maxTriggerNameLength (as shown here) 801 if (triggerName.length() > maxTriggerNameLength && maxTriggerNameLength > 0) { Does this check need to be in the code, or can you always execute the code that will verify the Triggername is not a duplicate?"
TagsNo tags attached.


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change