Re: searching illegal HTML

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 44410
interpreted = N
texte = >If the values in the databases are [url]'d you will need to [url] the fields >you are searching for .. > >&waGroup1datarq=[URL][field1][/URL] Actually you need to double-URL the values in your search *if* the values stored in the db are actually URLed values (for example, %96 is stored in the db instead of ñ) ... but this is a relatively rare situation.Here's a simple rule for eliminating most or all of these potential problems: Always [url] *every value* when appending, replacing and searching your db's.If you do this consistently, you will never have any problems searching for -- and finding -- the proper values, provided the values stored in your db have been entered via webdna and not by exporting a text file from some software like Excel (which tends to screw up some of the exported values if you're not very careful).Of course, if the values in your db are actually stored as URLed values (which means %96 appears in the db instead of ñ for example) then you would seem to be dealing with a different situation ... and in this case you would have to use one of the following searches:[search db=xxx.db&waf1datarq=[url][url]ñ[/url][/url]][search db=xxx.db&waf1datarq=[url]%96[/url]][search db=xxx.db&waf1datarq=%2596]Every one of these searches will produce the exact same results. They will all find the %96 value in the f1 field in the db. And of course the most common syntax is the middle one, because it clearly illustrates the proper technique of single-URLing the value you want to find in the db.:) Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.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:

    
  1. Re: searching illegal HTML (lb Lawrence 2002)
  2. Re: searching illegal HTML (lb Lawrence 2002)
  3. Re: searching illegal HTML (lb Lawrence 2002)
  4. Re: searching illegal HTML (Christer Olsson 2002)
  5. Re: searching illegal HTML (Brian Fries 2002)
  6. Re: searching illegal HTML (Gary Krockover 2002)
  7. Re: searching illegal HTML (Kenneth Grome 2002)
  8. Re: searching illegal HTML (lb Lawrence 2002)
  9. Re: searching illegal HTML (Donovan Brooke 2002)
  10. Re: searching illegal HTML (Donovan Brooke 2002)
  11. Re: searching illegal HTML (Kenneth Grome 2002)
  12. Re: searching illegal HTML (Kenneth Grome 2002)
  13. Re: searching illegal HTML (Michael Davis 2002)
  14. Re: searching illegal HTML (Michael Davis 2002)
  15. Re: searching illegal HTML (Donovan 2002)
  16. Re: searching illegal HTML (Alain Russell 2002)
  17. Re: searching illegal HTML (lb Lawrence 2002)
  18. Re: searching illegal HTML (Matthew Bohne 2002)
  19. Re: searching illegal HTML (Alain Russell 2002)
  20. Re: searching illegal HTML (lb Lawrence 2002)
  21. Re: searching illegal HTML (lb Lawrence 2002)
  22. Re: searching illegal HTML (lb Lawrence 2002)
  23. Re: searching illegal HTML (Alain Russell 2002)
  24. Re: searching illegal HTML (Donovan 2002)
  25. Re: searching illegal HTML (Matthew Bohne 2002)
  26. searching illegal HTML (lb Lawrence 2002)
>If the values in the databases are [url]'d you will need to [url] the fields >you are searching for .. > >&waGroup1datarq=[url][field1][/URL] Actually you need to double-URL the values in your search *if* the values stored in the db are actually URLed values (for example, %96 is stored in the db instead of ñ) ... but this is a relatively rare situation.Here's a simple rule for eliminating most or all of these potential problems: Always [url] *every value* when appending, replacing and searching your db's.If you do this consistently, you will never have any problems searching for -- and finding -- the proper values, provided the values stored in your db have been entered via webdna and not by exporting a text file from some software like Excel (which tends to screw up some of the exported values if you're not very careful).Of course, if the values in your db are actually stored as URLed values (which means %96 appears in the db instead of ñ for example) then you would seem to be dealing with a different situation ... and in this case you would have to use one of the following searches:[search db=xxx.db&waf1datarq=[url][url]ñ[/url][/url]][search db=xxx.db&waf1datarq=[url]%96[/url]][search db=xxx.db&waf1datarq=%2596]Every one of these searches will produce the exact same results. They will all find the %96 value in the f1 field in the db. And of course the most common syntax is the middle one, because it clearly illustrates the proper technique of single-URLing the value you want to find in the db.:) Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.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/ Kenneth Grome

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:

Grep and <> (2005) & in Lookups (1997) WebCatalog and WebTen (1997) Mass Mail (2000) New [If] command question (2000) WebCat2: Items xx to xx shown, etc. (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Date comparison using showif (2003) can WC render sites out? (1997) unsubscribe (2000) Using [showif] (2000) Problems reading files created by WC (1997) Backwards list behavior ... (1997) Kaaaaahhhhhhhnnnnnnn! (1997) Dark Horse Comics success story (1997) Forcing Search w/ URL (1999) Math with Time (1997) Emailer Question (1998) Problem 2: Prefs file... (1997) trouble updating records in database (1998)