Re: spaces in db

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 39975
interpreted = N
texte = well hmm, I have been spending as much time with the docs as my job allows. I've looked over some of these briefly. After looking at them again I think wbrk= could be the key yet I still am wary about coding it. (however it is academic to me at this point since I already edited the db.) the docs on this *are* a bit confusing. I am not sure a space can be defined in a custom word break context.?? &wofieldnamedata=graph&fieldnamewbrk= &asfieldnamesort=1Do I just put a space in the context? ..%20?? Also, it doesn't see just extra spaces.If I am searching for 305 in the database. and I have:305_FET____ in the db. and 305___ (_ being spaces)then a wbrk=_ could still find 305_FET____ before it finds 305___ right? that would be bad.yea, I know I have a lot to learn but this is some of the reason why I post to the list.The ideal thing would be to munge a space between words yet munge the spaces after the words.However, if I think about it, this is asking a search to be pretty picky. Maybe the best answer is to have a database with the correct info in it. whole word match (can be modified with wbrk to define word-break characters) Descriptionword=ww looks for graphic and will not find it inside phrases such as: I like typographic conventions. It will be found inside This is a graphic.John Peacock wrote:> Donovan Brooke wrote: > > > > Well, just a FYI note, > > I ended up going through the 2500 SKU's we have and just editing out the spaces. I thought about using > > a bw comparison in the search but I think that would have found more than one item. > > > > seems to me that with WebDNA's advanced search cababilities that there would be a solution for this > > but I guess not. (comparison that says its OK if there is spaces in field. just ingnore them.) > > Since you didn't post any code for what you are trying to do, there is little > anyone can do to help you. WebCat is perfectly capable of search for words, > substrings, etc. irregardless of extraneous spaces. You need to spend some > time with the docs, specifically the section on searching. The docs are not > the best in the world, but they do contain all of the information you are > looking for. Specifically look at Searching/Word Breaks. > > John > > ---- Donovan D. Brooke Systems Administrator/ Assc. Art Director Epsen Hillmer Graphics------------------------------------------------------------- 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:

    
  1. Re: spaces in db (Kelly Samuell 2001)
  2. Re: spaces in db (John Peacock 2001)
  3. Re: spaces in db (Donovan Brooke 2001)
  4. Re: spaces in db (Donovan Brooke 2001)
  5. Re: spaces in db (Donovan Brooke 2001)
  6. Re: spaces in db (kelly Samuell 2001)
  7. Re: spaces in db (John Peacock 2001)
  8. Re: spaces in db (Donovan Brooke 2001)
  9. Re: spaces in db (Andrew Simpson 2001)
  10. spaces in db (Donovan Brooke 2001)
well hmm, I have been spending as much time with the docs as my job allows. I've looked over some of these briefly. After looking at them again I think wbrk= could be the key yet I still am wary about coding it. (however it is academic to me at this point since I already edited the db.) the docs on this *are* a bit confusing. I am not sure a space can be defined in a custom word break context.?? &wofieldnamedata=graph&fieldnamewbrk= &asfieldnamesort=1Do I just put a space in the context? ..%20?? Also, it doesn't see just extra spaces.If I am searching for 305 in the database. and I have:305_FET____ in the db. and 305___ (_ being spaces)then a wbrk=_ could still find 305_FET____ before it finds 305___ right? that would be bad.yea, I know I have a lot to learn but this is some of the reason why I post to the list.The ideal thing would be to munge a space between words yet munge the spaces after the words.However, if I think about it, this is asking a search to be pretty picky. Maybe the best answer is to have a database with the correct info in it. whole word match (can be modified with wbrk to define word-break characters) Descriptionword=ww looks for graphic and will not find it inside phrases such as: I like typographic conventions. It will be found inside This is a graphic.John Peacock wrote:> Donovan Brooke wrote: > > > > Well, just a FYI note, > > I ended up going through the 2500 SKU's we have and just editing out the spaces. I thought about using > > a bw comparison in the search but I think that would have found more than one item. > > > > seems to me that with WebDNA's advanced search cababilities that there would be a solution for this > > but I guess not. (comparison that says its OK if there is spaces in field. just ingnore them.) > > Since you didn't post any code for what you are trying to do, there is little > anyone can do to help you. WebCat is perfectly capable of search for words, > substrings, etc. irregardless of extraneous spaces. You need to spend some > time with the docs, specifically the section on searching. The docs are not > the best in the world, but they do contain all of the information you are > looking for. Specifically look at Searching/Word Breaks. > > John > > ---- Donovan D. Brooke Systems Administrator/ Assc. Art Director Epsen Hillmer Graphics------------------------------------------------------------- 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/ Donovan Brooke

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:

Pithy questions on webcommerce & siteedit (1997) Change to 5.0 per website licensing (2003) Tracking inbound links for discounts (1997) Emailer (1997) Emailer on NT! (1998) Form/HTML Help (2000) No. of items in shopping cart (2000) emailer setup (1997) sandboxes with 6.0 (2004) Anybody see this before? (2006) Problems with [Search] param - Mac Plugin b15 (1997) writefiles (1999) calculating tax rates, mail order solutions and version 2 (1997) Nested tags count question (1997) Show first couple of lines. (2003) Summing fields (1997) list cookies and list http headers (1997) WCS Newbie question (1997) [shell] oddity (2002) Alternating colors (1997)