Re: searches with dash, period etc.

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 25948
interpreted = N
texte = My tests indicate that the 'WBRK' feature actually replaces (rather than adds to) the list of default separators. So specifying ..&FIELDNAMEwbrk=*, &... causes the dash char to no longer be considered a wordbreak character for that field(but will only consider asterisks and spaces as delimiters). This would allow me to continue to use wo in my searches of that field rather than switching to ws in cases where I want r-3400 to be treated as one word.Is this true? (if true, might be helpful to add the clarification to the manual's wordbreak section).Thanks, John B.------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Associated Messages, from the most recent to the oldest:

    
  1. Re[3]: searches with dash, period etc. (back form politenes (jpeacock@univpress.com 2000)
  2. Re: searches with dash, period etc. (John Bennett 2000)
  3. Re: searches with dash, period etc. (John Hill 2000)
  4. Re[2]: searches with dash, period etc. (back form politenes (Marty Schmid 2000)
  5. Re[2]: searches with dash, period etc. (back form politenes (jpeacock@univpress.com 2000)
  6. Re: searches with dash, period etc. (back form politeness) (John Hill 2000)
  7. Re: searches with dash, period etc. (back form politeness) (Marty Schmid 2000)
  8. Re: searches with dash, period etc. (Marty Schmid 2000)
  9. Re: searches with dash, period etc. (Kenneth Grome 2000)
  10. Re: searches with dash, period etc. (Joseph D'Andrea 2000)
  11. Re: searches with dash, period etc. (John Hill 2000)
  12. Re: searches with dash, period etc. (John Hill 2000)
  13. Re: searches with dash, period etc. (Kenneth Grome 2000)
  14. searches with dash, period etc. (John Bennett 2000)
My tests indicate that the 'WBRK' feature actually replaces (rather than adds to) the list of default separators. So specifying ..&FIELDNAMEwbrk=*, &... causes the dash char to no longer be considered a wordbreak character for that field(but will only consider asterisks and spaces as delimiters). This would allow me to continue to use wo in my searches of that field rather than switching to ws in cases where I want r-3400 to be treated as one word.Is this true? (if true, might be helpful to add the clarification to the manual's wordbreak section).Thanks, John B.------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 John Bennett

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:

PowerKey and PageSentry not playing nice (2000) Not really WebCat (1997) There's a bug in the math context ... (1997) WebDNA Running Out of RAM? (2004) RE: protect tag on NT (1997) WebCat Bulletin Board Solution ? (1998) WebDNA 4.5.1 Now Available (2003) Removing [showif] makes a big difference in speed (1997) Can he do that? (1998) HELP WITH DATES (1997) Summing fields (1997) It just Does't add up!!! (1997) WebCommerce: Folder organization ? (1997) WebCat2b13MacPlugIn - more [date] problems (1997) WebCat and image maps (1997) No luck with taxes (1997) (1997) Re:Email Problem (1997) Generating unique SKU from [cart] (1997) ConverChars (1999)