Not sure if this is the correct spot for this, but while upgrading to 6.0.2, I came across an error concerning the a constraint missing for a table in the database. When I went looking for the constraint, there was a Constraint that was oddly named. I have since fixed the issue and upgraded successfully.
To get the details on the upgrade problem and solution, see this topic
The constraints in other tables have fallen under a similar naming convention, if you can call it a convention. Here are a couple of examples:
DF__cmsConten__thumb__7F60ED59
DF__cmsMacro__macroC__108B795B
etc.
My concern is that even though the upgrade was successful, this could cause long term problems. I am not sure how they came to be named in this fashion, but the upgrade itself only complained of the one listed in the topic linked above. Any insight is appreciated. Thanks in advance.
SQL Database - Constraints in tables named oddly
Not sure if this is the correct spot for this, but while upgrading to 6.0.2, I came across an error concerning the a constraint missing for a table in the database. When I went looking for the constraint, there was a Constraint that was oddly named. I have since fixed the issue and upgraded successfully.
To get the details on the upgrade problem and solution, see this topic
The constraints in other tables have fallen under a similar naming convention, if you can call it a convention. Here are a couple of examples:
My concern is that even though the upgrade was successful, this could cause long term problems. I am not sure how they came to be named in this fashion, but the upgrade itself only complained of the one listed in the topic linked above. Any insight is appreciated. Thanks in advance.
Sean
is working on a reply...