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...DNN Platform (o...DNN Platform (o...Changing the default database tables.Changing the default database tables.
Previous
 
Next
New Post
3/6/2009 4:24 AM
 

Hello everyone!

Ok here's a really cool question. Is it "safe" to change the default database tables of dotnetnuke?

I want to add a few columns on the user profile table, is that ok? Im sure removing columns would cause some problems, but is adding columns ok?

Thanks

Paul

 
New Post
3/6/2009 7:28 AM
 

from memory you can add columns to the user profile - goto user accounts under admin - click on manage profile properties then click add new profile property.

You can also delete existing properties. You do not need to make any changes to the database

 
New Post
3/6/2009 8:56 AM
 

No, it is NOT SAFE to alter the DotNetNuke tables.  It is generally a bad idea to make any modifications to the DotNetNuke core framework.

As John pointed out, there are tools built into DotNetNuke to add profile properties and other items.  Use them. 




Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
3/6/2009 11:02 AM
 

john salmon wrote
 

from memory you can add columns to the user profile - goto user accounts under admin - click on manage profile properties then click add new profile property.

You can also delete existing properties. You do not need to make any changes to the database

Adding to John's info...
The DNN user properties are split into "User Credential" properties and "User Profile" properties.  The Credential properties are "hard-coded" as dedicated table columns in the DB.  The Profile properties are dynamic -- you do not have the simple "one-table-column-per-property" as you do for credentials.  There is some overlap between Credentials and Profile (FirstName and LastName appear in both, for instance).  Such overlaps are actually stored twice but are kept in synch by DNN code -- this is one example of why you always want to try to use existing DNN objects and methods rather than write your own versions.
 
To summarize:  Adding a custom user profile field does NOT add a new column to a table in the DB.  If you're manipulating profile fields from your own custom programming code then be sure to tap into the existing DNN objects/methods for doing so.
 
Cheers!
-mamlin


esmamlin atxgeek.me
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Changing the default database tables.Changing the default database tables.


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