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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Registration & User Module ComplaintsRegistration & User Module Complaints
Previous
 
Next
New Post
11/2/2006 6:33 PM
 
i'm building a myspace-type website and i personally love the idea of 'Display Name'.   this gives my members the ability to change their name without touching their username.

 
New Post
11/2/2006 6:35 PM
 
The problem with that, how I see it, is that the field is not unique - you can have multiple users with the same display name.
 
New Post
11/3/2006 12:50 PM
 
I'm pretty sure the 'Display Name' is there only for backward compatibility with older modules.
 
New Post
11/4/2006 12:11 AM
 
Display Name avoids using SQL logic for combination of FirstName + LastName (which improves performance). Having this as part of registration also offers things like the ability for a user to set their own alias in a community.

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
11/4/2006 5:13 AM
 

If I understand you correctly you say that doing a 'SELECT DisplayName FROM Users' is so much faster than 'SELECT FirstName,LastName FROM Users' that it must be mandatory?

I would very much like the option to disable it as it confuses my users a whole lot more than it helps them. I understand that another argument would be for backwards compatibility, but shouldn't it be up to the system integrators to decide if they want this or not? Well, it does bring up an other issue on how rule-bound mod development is. This is the part where you'll have to excuse me as I am clearly treading into unknown territory (yet) aka mod development... bear with me... Aren't there guidelines that give the developers directions on what to use and what not to? If it is a field kept for compatibility reasons I see no reason to keep it as a mandatory field. If a module tries to access a non-existant field a proper error handling process should be in place to handle that and allow the integrators to circuimvent that requirement if at all possible.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Registration & User Module ComplaintsRegistration & User Module Complaints


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