Re: The word TYPE in search contexts and fields

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16467
interpreted = N
texte = At 2:05 PM -0800 3/6/98, John Hill is rumored to have typed: > 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.Sometimes I do a find and replace in a database like so:[REPLACE db=/DB.db&neSKUdatarq=[BLANK]&eqINVdatarq=3&neTYPEdatarq=ant]INV3=5[/REPLACE]T his sometimes ignores the neTYPEdatarq arg.When I use this (TYPE field coming first), [REPLACE db=/DB.db&neTYPEdatarq=ant&neSKUdatarq=[BLANK]&eqINVdatarq=3]INV3=5[/REPLACE]e verything works fine.[SEARCH db=/MYDB.db&WATITLEdatarq=concrete&TITLEword=ww&neTYPEdatarq=ant] [FOUNDITEMS] [TITLE], [TYPE]
[/FOUNDITEMS] [/SEARCH]has produced results with TYPE=ant, but using [SEARCH db=/MYDB.db &neTYPEdatarq=ant&WATITLEdatarq=concrete&TITLEword=ww] doesn't.I'm never able to reproduce it on command, but I know I'm not imagining it. This all takes place when I'm using just small snippits of code on a test page.It's weird.MichaelMichael 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/ 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)
At 2:05 PM -0800 3/6/98, John Hill is rumored to have typed: > 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.Sometimes I do a find and replace in a database like so:[REPLACE db=/DB.db&neSKUdatarq=[BLANK]&eqINVdatarq=3&neTYPEdatarq=ant]INV3=5[/REPLACE]T his sometimes ignores the neTYPEdatarq arg.When I use this (TYPE field coming first), [REPLACE db=/DB.db&neTYPEdatarq=ant&neSKUdatarq=[BLANK]&eqINVdatarq=3]INV3=5[/REPLACE]e verything works fine.[SEARCH db=/MYDB.db&WATITLEdatarq=concrete&TITLEword=ww&neTYPEdatarq=ant] [founditems] [TITLE], [TYPE]
[/FOUNDITEMS] [/SEARCH]has produced results with TYPE=ant, but using [SEARCH db=/MYDB.db &neTYPEdatarq=ant&WATITLEdatarq=concrete&TITLEword=ww] doesn't.I'm never able to reproduce it on command, but I know I'm not imagining it. This all takes place when I'm using just small snippits of code on a test page.It's weird.MichaelMichael 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/ Michael Winston

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:

Reversed words (1997) [searchString] (1997) Not reading code (1997) taxTotal problem (1998) Thanks Grant (1997) Multiple prices (1997) Searching multiple Databases (1997) A Suggestion? (1998) [HIDEIF] inside [FOUNDITEM] (1997) group field search problem (2000) Intermitent problem using [referrer] (1997) Counting LineItems (2000) OLD ORDERS (1998) Calendar using WebCatalog? (1997) SiteEdit Pro Update Announcement (1997) page redirect in webDNA (1997) form data submission gets truncated (1997) Help with Shipping Costs (1997) WebCommerce: Folder organization ? (1997) Help name our technology! (1997)