Re: The word TYPE in search contexts and fields

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16463
interpreted = N
texte = Yes, it is smart enough to distingush between eqshiptypedata= and shiptype= (that is, a field named shiptype and ship). The problem is probably something more subtle. What sort of a search are you doing, what is being returned, and what do you expect? John.>I have several (well, two) fields in my main database called TYPE and >SHIPTYPE. Recently I've been noticing some errors cropping up when I use >these fields in search arguements (or replace, etc.) > >I think it's causing conflict with the FIELDtype= arguement. >Is WebCat smart enough to parse the part of eqSHIPTYPEdatarq so that it >realizes that I don't have a field called EQSHIP and it's of some type? > >This is causing a few problems, and I'd like to fix it as soon as I can. >Finding and replacing field names would be *very* cumbersome. > >Michael > >Michael Winston *By Phone!: (503)/652/8815 x341 >Internet Coordinator *By e-mail!: michaelw@dhorse.com >Dark Horse Comics, Inc. *By web!: http://www.dhorse.com/ John A. Hill, V.P. Marketing Pacific Coast Software eCommerce / Web Developer Tools http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: The word TYPE in search contexts and fields (Michael Winston 1998)
  2. Re: The word TYPE in search contexts and fields (John Hill 1998)
  3. Re: The word TYPE in search contexts and fields (Michael Winston 1998)
  4. Re: The word TYPE in search contexts and fields (John Hill 1998)
  5. The word TYPE in search contexts and fields (Michael Winston 1998)
Yes, it is smart enough to distingush between eqshiptypedata= and shiptype= (that is, a field named shiptype and ship). The problem is probably something more subtle. What sort of a search are you doing, what is being returned, and what do you expect? John.>I have several (well, two) fields in my main database called TYPE and >SHIPTYPE. Recently I've been noticing some errors cropping up when I use >these fields in search arguements (or replace, etc.) > >I think it's causing conflict with the FIELDtype= arguement. >Is WebCat smart enough to parse the part of eqSHIPTYPEdatarq so that it >realizes that I don't have a field called EQSHIP and it's of some type? > >This is causing a few problems, and I'd like to fix it as soon as I can. >Finding and replacing field names would be *very* cumbersome. > >Michael > >Michael Winston *By Phone!: (503)/652/8815 x341 >Internet Coordinator *By e-mail!: michaelw@dhorse.com >Dark Horse Comics, Inc. *By web!: http://www.dhorse.com/ John A. Hill, V.P. Marketing Pacific Coast Software eCommerce / Web Developer Tools http://www.smithmicro.com John Hill

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:

Date calculation problems (1997) case sensitivity in lookups (1997) NT 4.0/IIS WebCat Installation (1998) Ok here is a question? (1997) [SHOWIF]s and empty arguments (1997) SSL with IIS 4.0 (1998) question about checkboxes (1999) Limitations on fields? Server is crashing (1997) SV: WebCat on Linux (2000) raw field names (2001) multiple databases (1997) Using Cookie for client specific info? (1997) WebCat2 - [format thousands] (1997) The code, one more time. (2003) Maybe off topic but how to charge (1997) hidden databases (2000) [WebDNA] Weird issue with ADD (2018) [shipCost] math formula? (1997) preference to using Apache 2.x or 1.3.x with WebDNA 6.0? (2004) Calculating days, hours, minutes ago (2004)