[support] Doubt on Index and Primary key

[Pierre Rineau]

Le vendredi 18 mars 2011 à 08:15 -0700, Metzler, David a écrit :
> Pierre is spot on here. 
> 
> That is why most dbas would advise against storing this data in a comma separated list in a single field.  An index cannot really be used to search within the text cause you are forcing to examine every row anyway.  I can't programtically say lets start with the N's, now is there a nokia in there (that's an oversimplification intentionally to make a point). Rather I would make a single skill table that housed the values. If UID is the primary key for the resume, then you'd make a table with 
> 
> On a separate note, you do understand that the site that you're talking about building could be done without you writing ANY code? Basically the site you've described can be implemented with content_profile, cck and views modules, allowing you to build custom content types that are tied (one per user).  You could then use taxonomys for skill sets an all this would be written for you?
> 
> Dave

Dave is right about the fact this simple business stuff could be done in
many ways using D6 existing modules (even only with core and taxonomy)
or D7 fields.

But, if you really want to learn technical aspects of SQL and/or Drupal
development, this is a good thing to start with this kind of simple
business stuff.

Pierre.