Re: Looping Search
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66766
interpreted = N
texte = Have the supervisor field as an ID, with a related db to relate ID and name. Then if the person gets demoted or leaves have a means to do a (if appropriate) global replace [replacefound] with the new ID for the affected people. Make it part of the process when a person is removed that the people under them have to be reassigned. Maybe even have anther field to denote if this is a top level person or not, that way you can easily exclude or include them in your searches. Clint Davis wrote: > I *do* have a field in the database where each person's immediate supervisor > is listed. Right now, Person 1 is hard coded into the page. A [search] for > anyone whose immediate supervisor is Person 1 yields the Person 2 listing > and so on down the chain. This works unless someone at the top is removed: > if Person 2 left, Persons 3, 8, and 11 would have to be reassigned to Person > 1 as their immediate supervisor, or the whole chart would break. > > > On 4/5/06 2:57 PM, "Pat McCormick"
wrote: > > >> Why not just have a field for immediate supervisor for every Person? >> A demotion simply means changing the supervisor field. Or i guess it >> could also mean coming to a stop. (get it? demotion? anyone?) >> >> >> On Apr 5, 2006, at 2:24 PM, Clint Davis wrote: >> >> >>> I need to setup and org chart like this: >>> >>> Person 1 >>> -----Person 2 >>> ----------Person 3 >>> ---------------Person 4 >>> ---------------Person 5 >>> ---------------Person 6 >>> ---------------Person 7 >>> ----------Person 8 >>> ---------------Person 9 >>> ---------------Person 10 >>> ----------Person 11 >>> ---------------Person 12 >>> ---------------Person 13 >>> ---------------Person 14 >>> >>> All of these people have a record in the personnel database with a field for >>> their immediate supervisor. Can this be done with a [loop]'ed [search] versus >>> my current nested [search]es? I don't want it to break if Person 3 gets >>> demoted, for example. >>> ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Have the supervisor field as an ID, with a related db to relate ID and name. Then if the person gets demoted or leaves have a means to do a (if appropriate) global replace [replacefound] with the new ID for the affected people. Make it part of the process when a person is removed that the people under them have to be reassigned. Maybe even have anther field to denote if this is a top level person or not, that way you can easily exclude or include them in your searches. Clint Davis wrote: > I *do* have a field in the database where each person's immediate supervisor > is listed. Right now, Person 1 is hard coded into the page. A [search] for > anyone whose immediate supervisor is Person 1 yields the Person 2 listing > and so on down the chain. This works unless someone at the top is removed: > if Person 2 left, Persons 3, 8, and 11 would have to be reassigned to Person > 1 as their immediate supervisor, or the whole chart would break. > > > On 4/5/06 2:57 PM, "Pat McCormick" wrote: > > >> Why not just have a field for immediate supervisor for every Person? >> A demotion simply means changing the supervisor field. Or i guess it >> could also mean coming to a stop. (get it? demotion? anyone?) >> >> >> On Apr 5, 2006, at 2:24 PM, Clint Davis wrote: >> >> >>> I need to setup and org chart like this: >>> >>> Person 1 >>> -----Person 2 >>> ----------Person 3 >>> ---------------Person 4 >>> ---------------Person 5 >>> ---------------Person 6 >>> ---------------Person 7 >>> ----------Person 8 >>> ---------------Person 9 >>> ---------------Person 10 >>> ----------Person 11 >>> ---------------Person 12 >>> ---------------Person 13 >>> ---------------Person 14 >>> >>> All of these people have a record in the personnel database with a field for >>> their immediate supervisor. Can this be done with a [loop]'ed [search] versus >>> my current nested [search]es? I don't want it to break if Person 3 gets >>> demoted, for example. >>> ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Dale Lists
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] PHP and WebDNA together? (2011)
2.0 Info (1997)
[WebDNA] Libmysql.dll error (2009)
2.0Beta Command Ref (can't find this instruction) (1997)
Emailer Error Question (1998)
AAgghh!! Help, please. SSL strikes again. (1997)
[text] variable assignment within [search] context (2000)
Mondo amounts of Mail [long] (1999)
Million product store (2003)
[WebDNA] WebDNA 7 fastcgi fails to start (2011)
Webstar 1.3.1 PPC (1997)
Tab Charactor (1997)
delete a file? (1998)
(1997)
Sort Order on a page search (1997)
test mail (2004)
Netscape v. IE (1997)
WebCat2.0b15-to many nested [xx] tags (1997)
RE: Going to anchors within a template page (1997)
[subtotal] and others (1997)