Re: [WebDNA] Text Variable in Search

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105377
interpreted = N
texte = This is a multi-part message in MIME format. ------=_NextPart_000_0021_01CB1080.7F18A150 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable correction (forgot an ampersand): [search db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3Dnum&SKUsort=3D1] From: Dan Strong=20 Sent: Sunday, June 20, 2010 1:54 PM To: talk@webdna.us=20 Subject: Re: [WebDNA] Text Variable in Search From: sgbc cebu=20 Sent: Sunday, June 20, 2010 1:29 PM To: talk@webdna.us=20 Subject: [WebDNA] Text Variable in Search Not totally sure what you're trying to do, but your argument (ge) = requires that SKU is *greater than or equal to* 0, so you also need to = tell the search query to treat the SKU field as a number for this = search, otherwise it can't make a numerical comparison: [search db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3DnumSKUsort=3D1] [founditems] [showif [url][Slideshow][/url]=3D[url]YES[/url]] [text]YES=3DRockU[/text] [/showif] [/founditems] [/search] [YES] Also, not sure why you double-bracketed [Slideshow], but I removed the = second set of brackets, and if there are more than one SKUs that are = greater than or equal to 0 then you're going to get the value for the = last record in the [founditems] loop. If you are just making an example for learning purposes then hopefully = my code will help your understanding, but if this is fr an actual = project, I'd want to know more about what you're trying to do before I = said my code was the best solution.=20 -Dan ---------------------------------------- Had difficulty of pulling a text variable via a database. Please consider this code: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D [text]YES=3DRockU[/text] [search db=3Dinc/content.db&geSKUdata=3D0&SKUsort=3D1] [founditems] [[Slideshow]] [/founditems] [/search] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D Where [SlideShow] either will get a YES or a NO from database. The problem is when [SlideShow] tells "YES". It will appear "[Yes]" on the page instead of "Rocku" Thanks ------=_NextPart_000_0021_01CB1080.7F18A150 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
correction (forgot an = ampersand):
[search=20 db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3Dnum&SKUsort=3D1]<= /FONT>
 

From: Dan Strong
Sent: Sunday, June 20, 2010 1:54 PM
To: talk@webdna.us
Subject: Re: [WebDNA] Text Variable in = Search

 

From: sgbc cebu
Sent: Sunday, June 20, 2010 1:29 PM
To: talk@webdna.us
Subject: [WebDNA] Text Variable in Search
Not totally sure what you're trying to = do, but your=20 argument (ge) requires that SKU is *greater than or equal to* 0, so you = also=20 need to tell the search query to treat the SKU field as a number = for this=20 search, otherwise it can't make a numerical comparison:
 
[search=20 db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3DnumSKUsort=3D1]
&n= bsp;   [founditems]
        [showif = [url][Slideshow][/url]=3D[url]YES[/url]]
           &n= bsp;[text]YES=3DRockU[/text]
        [/showif]
    [/founditems]
[/search]
 
[YES]
 
Also, not sure why you double-bracketed = [Slideshow], but I removed the second set of brackets, and if there are = more=20 than one SKUs that are greater than or equal to 0 then you're going to = get the=20 value for the last record in the [founditems] loop.
 
If you are just making an example for = learning=20 purposes then hopefully my code will help your understanding, but = if this=20 is fr an actual project, I'd want to know more about what you're trying = to do=20 before I said my code was the best solution. 
 
-Dan
----------------------------------------


Had difficulty of pulling a text variable via a=20 database.

Please consider this=20 code:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

[text]YES=3DRockU[/text]

[search=20 db=3Dinc/content.db&geSKUdata=3D0&SKUsort=3D1]
[founditems]
[[Slideshow]]

[/founditems]
[/search]

=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D

Where=20 [SlideShow] either will get a YES or a NO from database.

The = problem is=20 when [SlideShow] tells "YES".
It will appear "[Yes]" on the page = instead of=20 "Rocku"

Thanks
------=_NextPart_000_0021_01CB1080.7F18A150-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Text Variable in Search (sgbc cebu 2010)
  2. Re: [WebDNA] Text Variable in Search ("Terry Wilson" 2010)
  3. Re: [WebDNA] Text Variable in Search ("Dan Strong" 2010)
  4. Re: [WebDNA] Text Variable in Search ("Dan Strong" 2010)
  5. [WebDNA] Text Variable in Search (sgbc cebu 2010)
This is a multi-part message in MIME format. ------=_NextPart_000_0021_01CB1080.7F18A150 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable correction (forgot an ampersand): [search db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3Dnum&SKUsort=3D1] From: Dan Strong=20 Sent: Sunday, June 20, 2010 1:54 PM To: talk@webdna.us=20 Subject: Re: [WebDNA] Text Variable in Search From: sgbc cebu=20 Sent: Sunday, June 20, 2010 1:29 PM To: talk@webdna.us=20 Subject: [WebDNA] Text Variable in Search Not totally sure what you're trying to do, but your argument (ge) = requires that SKU is *greater than or equal to* 0, so you also need to = tell the search query to treat the SKU field as a number for this = search, otherwise it can't make a numerical comparison: [search db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3DnumSKUsort=3D1] [founditems] [showif [url][Slideshow][/url]=3D[url]YES[/url]] [text]YES=3DRockU[/text] [/showif] [/founditems] [/search] [YES] Also, not sure why you double-bracketed [Slideshow], but I removed the = second set of brackets, and if there are more than one SKUs that are = greater than or equal to 0 then you're going to get the value for the = last record in the [founditems] loop. If you are just making an example for learning purposes then hopefully = my code will help your understanding, but if this is fr an actual = project, I'd want to know more about what you're trying to do before I = said my code was the best solution.=20 -Dan ---------------------------------------- Had difficulty of pulling a text variable via a database. Please consider this code: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D [text]YES=3DRockU[/text] [search db=3Dinc/content.db&geSKUdata=3D0&SKUsort=3D1] [founditems] [[Slideshow]] [/founditems] [/search] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D Where [SlideShow] either will get a YES or a NO from database. The problem is when [SlideShow] tells "YES". It will appear "[Yes]" on the page instead of "Rocku" Thanks ------=_NextPart_000_0021_01CB1080.7F18A150 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
correction (forgot an = ampersand):
[search=20 db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3Dnum&SKUsort=3D1]<= /FONT>
 

From: Dan Strong
Sent: Sunday, June 20, 2010 1:54 PM
Subject: Re: [WebDNA] Text Variable in = Search

 

From: sgbc cebu
Sent: Sunday, June 20, 2010 1:29 PM
Subject: [WebDNA] Text Variable in Search
Not totally sure what you're trying to = do, but your=20 argument (ge) requires that SKU is *greater than or equal to* 0, so you = also=20 need to tell the search query to treat the SKU field as a number = for this=20 search, otherwise it can't make a numerical comparison:
 
[search=20 db=3Dinc/content.db&geSKUdata=3D0&SKUtype=3DnumSKUsort=3D1]
&n= bsp;   [founditems]
        [showif = [url][Slideshow][/url]=3D[url]YES[/url]]
           &n= bsp;[text]YES=3DRockU[/text]
        [/showif]
    [/founditems]
[/search]
 
[YES]
 
Also, not sure why you double-bracketed = [Slideshow], but I removed the second set of brackets, and if there are = more=20 than one SKUs that are greater than or equal to 0 then you're going to = get the=20 value for the last record in the [founditems] loop.
 
If you are just making an example for = learning=20 purposes then hopefully my code will help your understanding, but = if this=20 is fr an actual project, I'd want to know more about what you're trying = to do=20 before I said my code was the best solution. 
 
-Dan
----------------------------------------


Had difficulty of pulling a text variable via a=20 database.

Please consider this=20 code:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

[text]YES=3DRockU[/text]

[search=20 db=3Dinc/content.db&geSKUdata=3D0&SKUsort=3D1]
[founditems]
[[Slideshow]]

[/founditems]
[/search]

=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D

Where=20 [SlideShow] either will get a YES or a NO from database.

The = problem is=20 when [SlideShow] tells "YES".
It will appear "[Yes]" on the page = instead of=20 "Rocku"

Thanks
------=_NextPart_000_0021_01CB1080.7F18A150-- "Dan Strong"

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:

RE: webcat license???? (1997) Mac: LModelDirector bug fix (1997) Country & Ship-to address & other fields ? (1997) Thanks ! (1997) Here's how to kill a Butler Database. (1997) [OT] CSS div/span (2004) WC2f3 (1997) Serving images from databases (1998) Displaying photo attached to first record (1997) $Append for Users outside the ADMIN group (1997) Carts & Refering URLs (1997) [OT] Browser's search via javascript? (2003) What about an ends with operator? (2000) RequiredFields notes ... (1997) 2.1 Stuff (1998) Re:listfiles-looking for slick solution (1997) problems with 2 tags (1997) Major Security Hole (1998) Too Much Rootbeer Free Offer (1997) CASTEGORIES IN DIFFERENT FRAMES (1997)