Re: multi-table date sort problem thingy
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 45400
interpreted = N
texte = Yeah, yields the same results. Thanks. -- Patrick Junkroski President/CEO http://www.vsm.net (239) 642.0304> From: Gary Krockover
> Reply-To: (WebCatalog Talk) > Date: Mon, 18 Nov 2002 15:34:22 -0600 > To: (WebCatalog Talk) > Subject: Re: multi-table date sort problem thingy > > Just a stab, but try this in your date search: > > [search > db=performances/performances.db&eqeventskudatarq=[sku]&perdatesort=1&perfdat > esdir=as&perfdatetype=date] > > GK > > Alright. Here's the variable for the search: > > > > The results page has several searches on it, depending on what is being > sought (there is a performing arts center, an orchestra AND a museum. > Here's the pertinent one (I added comments here for easier understanding) > > > [search db=ThePhil.db&[formvariables name=_&exact=F][getchars > start=2][name][/getchars]=[url][value][/url]&[/formvariables]wseventtype2dat > a=[_wsEventType1data]&startat=[startat]] > > > > > [founditems] > > [showif [numfound]=1] > [redirect url=Display.tpl?SKU=[URL][SKU][/URL]] > [/showif] > > > [hideif [numfound]=1] > > > > | href=Display.tpl?SKU=[URL][SKU][/URL]>[EventName] | >
> [/hideif] > [/founditems] > [/search] > > Thanks, > -- > Patrick Junkroski > http://www.vsm.net > (239) 642.0304 > > > >> From: Donovan Brooke >> Reply-To: (WebCatalog Talk) >> Date: Mon, 18 Nov 2002 15:15:02 -0600 >> To: (WebCatalog Talk) >> Subject: Re: multi-table date sort problem thingy >> >> would help if we saw the code me thinks. >> If this is one search it could be an Allhit=1 scenereo. >> (sorting per rank) >> >> Donovan >> >> >> >> PatrickJ wrote: >> >>> Long one. Ready? >>> >>> One of our clients has an events database, in three tables: >>> >>> Table 1 is an Artists database which contains only names: >>> Cosby, Bill >>> Cirque Eloize, >>> Miami City Ballet >>> >>> This table is used to generate a select menu for users to search for a >>> specific performer. >>> >>> Table 2 is the actual Event db with, among other fields, Billing > (which >>> replicates what's in the artist db - there is a reason, don't worry), >>> Description, Underwriter, etc. >>> >>> Table 3 is the performance dates table. >>> >>> So...If I search for Bill Cosby from the select menu, that name is sent > to >>> the next page to look for a match in the Billing field of the > events.db. >>> Using the SKU (primary key) for that event, it looks for all related >>> performances in the performance db and lists them in chronological order. >>> This works perfectly when there is one match for the first part of the >>> search. Example: >>> >>> Bill Cosby >>> April 17, 2003, 7PM >>> >>> Bill Cosby >>> April 18, 2003, 3 PM >>> >>> Bill Cosby >>> April 18, 2003, 7 PM >>> >>> However, when more than one match is made on the FIRST part of the > search, I >>> can't sort by date properly. For instance, the Miami City Ballet has 5 >>> separate, unrelated shows, some with multiple performances. So, in my >>> search results, I get chronological listings *within each event* but not >>> overall. As below: >>> >>> Miami City Ballet #3: Coppélia: Ballet1s Comic Masterpiece >>> March 18, 2003, 8 p.m. >>> March 19, 2003, 8 p.m. >>> >>> The Neighborhood Ballroom >>> December 11, 2002, 8 p.m. >>> >>> Miami City Ballet #1: Some Balanchine Heroes >>> January 14, 2003, 8 p.m. >>> January 15, 2003, 8 p.m. >>> >>> George Balanchine's The Nutcracker >>> November 27, 2002, 8 p.m. >>> November 29, 2002, 8 p.m. >>> November 30, 2002, 8 p.m. >>> November 30, 2002, 2 p.m. >>> December 01, 2002, 2 p.m. >>> December 01, 2002, 7 p.m. >>> >>> In the example above, you can see that The Nutcracker, with all of its >>> dates, should be FIRST on the list, followed by The Neighborhood > Ballroom, >>> Balanchine's Heroes, and Comic Masterpiece. >>> >>> Because the performance dates are in a separate table, I have no way to >>> perform a sort on the order in which these events come up, rather only > for >>> the dates FOR each event. >>> >>> Does anyone understand my problem? If so, are there suggestions for how > I >>> can address this? >>> >>> TIA >>> -- >>> Patrick Junkroski >>> http://www.vsm.net >>> (239) 642.0304 > > > ------------------------------------------------------------- > 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://search.smithmicro.com/ ------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Yeah, yields the same results. Thanks. -- Patrick Junkroski President/CEO http://www.vsm.net (239) 642.0304> From: Gary Krockover > Reply-To: (WebCatalog Talk) > Date: Mon, 18 Nov 2002 15:34:22 -0600 > To: (WebCatalog Talk) > Subject: Re: multi-table date sort problem thingy > > Just a stab, but try this in your date search: > > [search > db=performances/performances.db&eqeventskudatarq=[sku]&perdatesort=1&perfdat > esdir=as&perfdatetype=date] > > GK > > Alright. Here's the variable for the search: > > > > The results page has several searches on it, depending on what is being > sought (there is a performing arts center, an orchestra AND a museum. > Here's the pertinent one (I added comments here for easier understanding) > > > [search db=ThePhil.db&[formvariables name=_&exact=F][getchars > start=2][name][/getchars]=[url][value][/url]&[/formvariables]wseventtype2dat > a=[_wsEventType1data]&startat=[startat]] > > > > > [founditems] > > [showif [numfound]=1] > [redirect url=Display.tpl?SKU=[url][SKU][/URL]] > [/showif] > > > [hideif [numfound]=1] > > > > | href=Display.tpl?SKU=[url][SKU][/URL]>[EventName] | >
> [/hideif] > [/founditems] > [/search] > > Thanks, > -- > Patrick Junkroski > http://www.vsm.net > (239) 642.0304 > > > >> From: Donovan Brooke >> Reply-To: (WebCatalog Talk) >> Date: Mon, 18 Nov 2002 15:15:02 -0600 >> To: (WebCatalog Talk) >> Subject: Re: multi-table date sort problem thingy >> >> would help if we saw the code me thinks. >> If this is one search it could be an Allhit=1 scenereo. >> (sorting per rank) >> >> Donovan >> >> >> >> PatrickJ wrote: >> >>> Long one. Ready? >>> >>> One of our clients has an events database, in three tables: >>> >>> Table 1 is an Artists database which contains only names: >>> Cosby, Bill >>> Cirque Eloize, >>> Miami City Ballet >>> >>> This table is used to generate a select menu for users to search for a >>> specific performer. >>> >>> Table 2 is the actual Event db with, among other fields, Billing > (which >>> replicates what's in the artist db - there is a reason, don't worry), >>> Description, Underwriter, etc. >>> >>> Table 3 is the performance dates table. >>> >>> So...If I search for Bill Cosby from the select menu, that name is sent > to >>> the next page to look for a match in the Billing field of the > events.db. >>> Using the SKU (primary key) for that event, it looks for all related >>> performances in the performance db and lists them in chronological order. >>> This works perfectly when there is one match for the first part of the >>> search. Example: >>> >>> Bill Cosby >>> April 17, 2003, 7PM >>> >>> Bill Cosby >>> April 18, 2003, 3 PM >>> >>> Bill Cosby >>> April 18, 2003, 7 PM >>> >>> However, when more than one match is made on the FIRST part of the > search, I >>> can't sort by date properly. For instance, the Miami City Ballet has 5 >>> separate, unrelated shows, some with multiple performances. So, in my >>> search results, I get chronological listings *within each event* but not >>> overall. As below: >>> >>> Miami City Ballet #3: Coppélia: Ballet1s Comic Masterpiece >>> March 18, 2003, 8 p.m. >>> March 19, 2003, 8 p.m. >>> >>> The Neighborhood Ballroom >>> December 11, 2002, 8 p.m. >>> >>> Miami City Ballet #1: Some Balanchine Heroes >>> January 14, 2003, 8 p.m. >>> January 15, 2003, 8 p.m. >>> >>> George Balanchine's The Nutcracker >>> November 27, 2002, 8 p.m. >>> November 29, 2002, 8 p.m. >>> November 30, 2002, 8 p.m. >>> November 30, 2002, 2 p.m. >>> December 01, 2002, 2 p.m. >>> December 01, 2002, 7 p.m. >>> >>> In the example above, you can see that The Nutcracker, with all of its >>> dates, should be FIRST on the list, followed by The Neighborhood > Ballroom, >>> Balanchine's Heroes, and Comic Masterpiece. >>> >>> Because the performance dates are in a separate table, I have no way to >>> perform a sort on the order in which these events come up, rather only > for >>> the dates FOR each event. >>> >>> Does anyone understand my problem? If so, are there suggestions for how > I >>> can address this? >>> >>> TIA >>> -- >>> Patrick Junkroski >>> http://www.vsm.net >>> (239) 642.0304 > > > ------------------------------------------------------------- > 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://search.smithmicro.com/ ------------------------------------------------------------- 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://search.smithmicro.com/
PatrickJ
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:
vCards for Contact management (2004)
Tracking (2004)
more Dreamweaver Extensions feedback (2000)
Sort Order on a page search (1997)
Showif for mulitple variations (1997)
emailer cc to figured out (1997)
Problems passing [SKU] with $Replace in 2.0 (1997)
Multiple Merchant Accounts? (1997)
"Could not establish connection with module" (2005)
Thanks Grant (1997)
removelineitems (2000)
SIMS & WebCat .... Alias Folder (2002)
too many nested tags ... (1997)
Search in 2 or more catalogs (1997)
RE: creating writefile data from a nested search (1997)
random random links (1999)
SKU lookup (1997)
Can't add a field (1998)
Re[2]: Date Time Oddness (1999)
[switch][case] (2004)