Another site that 4.0.1 seems to have broken
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 34255
interpreted = N
texte = I've got several sites that I inherited that were coded in 3.0.x and arenow having varying problems under 4.0.1. This one seems like it should be aneasy fix, but I've been staring at it for hours with my limited WebCatskills and experience and I can't figure out what the hell is going on.Any advice or help would be appreciated.THE BACKGROUND: The pages are a movie listings db. We get the data from another source eachweek. It worked fine last week. Then we updated to 4.0.1. I even triedreplacing this week's data with last week's, but that didn't change anythingabout this problem.It has 6 tables in one file, so every search must first search on FIELD1 tomatch the search to the correct table.The listing.hdr file names all of the fields: FIELD1 through FIELD 6table 4 (FIELD1=4) is the movie information table:FIELD1: table #FIELD2: Movie_Code (code # assigned to each movie)FIELD3: Movie_Name (title of the movie)FIELD4: RATING_CODE (a one-letter code for the MPAA Rating)table 6 (FIELD1=6) is the MPAA Ratings table:FIELD1: table #FIELD2: RATING_CODE (same as FIELD4 in the movie information table above)FIELD3: RATING (e.g., G, PG, PG-13, R, NC-17, X, etc.)THE PROBLEM: everything works except for the inner nested search below whichdoes the lookup in table 6 to find the corresponding MPAA Rating for theRating_Code from FIELD4 of the movie table. You can see I've got [FIELD4]displaying in that line (just for a test; it shouldn't display in the finalversion). *THAT* [FIELD4] displays the correct data, but the nested searchreturns data for [FIELD3] of table 6 *ONLY* if the code and rating is G,i.e., only if the *contents* of those two fields are equal!Did something change in 4.0.1 that would cause this?* * * Before I sent this I went to the listing.db file and changed the Rating(FIELD3 of table 6) of PG to P so it would match the one-letter code inrating_Code (FIELD2 of table 6 and FIELD4 of table 4). NOW, that nestedsearch will return P in the founditems! BUT, even though the R ratingalready matched the code (like the G rating), the R *DOES NOT* return.I have attached a copy of the listing.db (and listing.hdr) file in case youwant to test it.If you need to see the other files in the site (there are only 3 templatesand 2 include files in the whole thing, in addition to the .db and .hdrfiles).Thanks,Steve--------------------- CODE ------------------------ [formvariables] [showif [name]=Code] [search db=listing.db&eqFIELD1datarq=4&eqFIELD2datarq=[value]] [founditems] [FIELD3]> [FIELD4] ([searchdb=listing.db&eqFIELD1datarq=6&eqFIELD2datarq=[FIELD4]&max=1] [founditems] [FIELD3] [!]the problem field[/!] [/founditems] [/search]) [/founditems] [/search] [/showif] [/formvariables] --------------------- CODE ------------------------Thanks,Steve------------------------------------------------Steven JarvisWeb Developersjarvis@nwaonline.netMorning News of Northwest Arkansashttp://www.nwaonline.net-------------------------------------------------------------------------------------------------------------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:
|
- Another site that 4.0.1 seems to have broken (Steven Jarvis 2000)
|
I've got several sites that I inherited that were coded in 3.0.x and arenow having varying problems under 4.0.1. This one seems like it should be aneasy fix, but I've been staring at it for hours with my limited WebCatskills and experience and I can't figure out what the hell is going on.Any advice or help would be appreciated.THE BACKGROUND: The pages are a movie listings db. We get the data from another source eachweek. It worked fine last week. Then we updated to 4.0.1. I even triedreplacing this week's data with last week's, but that didn't change anythingabout this problem.It has 6 tables in one file, so every search must first search on FIELD1 tomatch the search to the correct table.The listing.hdr file names all of the fields: FIELD1 through FIELD 6table 4 (FIELD1=4) is the movie information table:FIELD1: table #FIELD2: Movie_Code (code # assigned to each movie)FIELD3: Movie_Name (title of the movie)FIELD4: RATING_CODE (a one-letter code for the MPAA Rating)table 6 (FIELD1=6) is the MPAA Ratings table:FIELD1: table #FIELD2: RATING_CODE (same as FIELD4 in the movie information table above)FIELD3: RATING (e.g., G, PG, PG-13, R, NC-17, X, etc.)THE PROBLEM: everything works except for the inner nested search below whichdoes the lookup in table 6 to find the corresponding MPAA Rating for theRating_Code from FIELD4 of the movie table. You can see I've got [FIELD4]displaying in that line (just for a test; it shouldn't display in the finalversion). *THAT* [FIELD4] displays the correct data, but the nested searchreturns data for [FIELD3] of table 6 *ONLY* if the code and rating is G,i.e., only if the *contents* of those two fields are equal!Did something change in 4.0.1 that would cause this?* * * Before I sent this I went to the listing.db file and changed the Rating(FIELD3 of table 6) of PG to P so it would match the one-letter code inrating_Code (FIELD2 of table 6 and FIELD4 of table 4). NOW, that nestedsearch will return P in the founditems! BUT, even though the R ratingalready matched the code (like the G rating), the R *DOES NOT* return.I have attached a copy of the listing.db (and listing.hdr) file in case youwant to test it.If you need to see the other files in the site (there are only 3 templatesand 2 include files in the whole thing, in addition to the .db and .hdrfiles).Thanks,Steve--------------------- CODE ------------------------ [formvariables] [showif [name]=Code] [search db=listing.db&eqFIELD1datarq=4&eqFIELD2datarq=[value]] [founditems] [FIELD3]> [FIELD4] ([searchdb=listing.db&eqFIELD1datarq=6&eqFIELD2datarq=[FIELD4]&max=1] [founditems] [FIELD3] [!]the problem field[/!] [/founditems] [/search]) [/founditems] [/search] [/showif] [/formvariables] --------------------- CODE ------------------------Thanks,Steve------------------------------------------------Steven JarvisWeb Developersjarvis@nwaonline.netMorning News of Northwest Arkansashttp://www.nwaonline.net-------------------------------------------------------------------------------------------------------------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/
Steven Jarvis
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:
[ot] iBook vs. 12" PB (2004)
Field name-subcategory (1997)
Unix Webcat Permission - Suggestions (2000)
any limitations on # of users.db entries (1999)
ShipCost Data Base (1998)
Editing Users.db (1997)
NT Version on IIS 4.0 (1997)
[WebDNA] XML Parsing Error Help (2010)
[quantity] - spoke too soon (1997)
Shopping cart now bad (1997)
& not allowed in db by definition? (1999)
Separate SSL Server (1997)
cart converting to scientific notation format (2001)
WC1.6 to WC2 date formatting (1997)
[format xs] freeze (1997)
Chown www:wheel Almost There WebCat 5 on itools 7 (2003)
WebCat2: multiple currency support (1997)
attachment stupidity... (2001)
[OT] Bush's Cyberensive (2003)
WebStar Questions ... (2000)