Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...default constraint namingdefault constraint naming
Previous
 
Next
New Post
6/19/2013 11:24 PM
 
While testing against 06.02.00 It appears the extension has created a default constraint using the incorrect object qualifier: TestQualifier_DF_DigArticleArticle_Rating

It appears that I create using the following naming:

[{objectQualifier}DF_DigArticleArticle_Rating]

This works on Azure, should this really be an error condition?  I would think just having the objectQualifier in the name should be good enough, no?

Thanks
Mike

 
New Post
6/19/2013 11:26 PM
 

Same for primary keys...

While testing against 06.02.00 It appears the extension has created a primary key using the incorrect object qualifier: TestQualifier_PK_DigArticleSource


Thanks

Mike

 
New Post
6/20/2013 3:54 AM
 
+1 on this. Is there any way so that we can validate this, or any sql server query format would be helpful.

Thanks
 
New Post
6/24/2013 4:06 PM
 
Hello Mike,

The Standard format for this is to have the Qualifier after the object type abbreviation. So for example the SQL objects and supported formats are:

Unique Constraint:
IX_{objectQualifier}ObjectName

Primary Key:
PK_{objectQualifier}ObjectName

Foreign Key:
FK_{objectQualifier}ObjectName

Default Constraint:
DF_{objectQualifier}ObjectName

Tables, Stored Procedures & Views:
{objectQualifier}ObjectName

If you look at the example on this page in the wiki: http://www.dotnetnuke.com/Resources/W...

You can see why this makes sense, in that example while creating a primary key on the table, the standard naming convention (used when auto generating scripts from SSMS) is to do PK_TableName. As you can see in the example, the Table name is {objectQualifier}DNNSimpleArticle_Article so the primary key for that table would be named PK_{objectQualifier}DNNSimpleArticle_Article.

Please let me know if you have any other questions.

Cheers,

Nathan Rover
 
New Post
6/24/2013 4:48 PM
 
So, it's going to remain an error if we don't choose the correct naming convention?  It's not simple to change something like that in an established module...

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...default constraint namingdefault constraint naming


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out