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...Foreign key - warningForeign key - warning
Previous
 
Next
New Post
6/28/2013 8:15 AM
 

Hi

I'm getting warning:
While testing against 06.00.00 it was detected that a DotNetNuke core SQL object (TestQualifier_Modules) was modified by this extension

I think it applies to SQL script that create foreign key:
ALTER TABLE {databaseOwner}[{objectQualifier}GS_ADProUserDirectory_Properties]
ADD CONSTRAINT FK_{objectQualifier}GS_ADProUserDirectory_Property_ModuleID FOREIGN KEY (ModuleID) REFERENCES {databaseOwner}[{objectQualifier}Modules](ModuleID)

How can I add foreign key constraint without warning message?

 
New Post
6/28/2013 8:29 AM
 
Hello,

You're correct, the warning in this case looks to be the result of a foreign key constraint. There isn't a way to add a foreign key to a core table without without raising this warning. The point of that check is just to bring attention to any possible modification to the core database objects. EVS is not identifying this as an error as it's perfectly acceptable to perform these types of modifications. It's simply there to make the user aware of what the extension is doing.

Please let me know if you have any other questions.

Cheers,

Nathan Rover
 
New Post
6/28/2013 4:19 PM
 
It usually is not the best practice to place a foreign key on core tables, but there are some situations where there is no other option.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/29/2013 5:07 AM
 

@Sebastian, @Nathan thanks for the answer.

EVS is a very helpful tool.

 
New Post
7/30/2013 7:02 AM
 
Sebastian Leupold wrote:
It usually is not the best practice to place a foreign key on core tables, but there are some situations where there is no other option.

I fully understand the consequences. 

Do you have a working strategy to delete records from the content of a custom module when the module itself is deleted by admin/cleanup/recycle bin? There is no such thing as a OnDeletModule event you can subscribe to...


XCESS expertise center b.v.
Regards,
Ernst Peter
LinkedIn Profile Ernst Peter Tamminga


XCESS: DNN/Evoq specialist, zie www.xcess.nl

Events 7.0.1 - Released
Reports 6.1.0 - Released
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsExtension Verif...Extension Verif...Foreign key - warningForeign key - warning


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