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:[REPLACEdb=/DB.db&neSKUdatarq=[BLANK]&eqINVdatarq=3&neTYPEdatarq=ant]INV3=5[/REPLACE]This sometimes ignores the neTYPEdatarq arg.When I use this (TYPE field coming first),[REPLACEdb=/DB.db&neTYPEdatarq=ant&neSKUdatarq=[BLANK]&eqINVdatarq=3]INV3=5[/REPLACE]everything 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 x341Internet Coordinator *By e-mail!: michaelw@dhorse.comDark Horse Comics, Inc. *By web!: http://www.dhorse.com/
Associated Messages, from the most recent to the oldest:
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:[REPLACEdb=/DB.db&neSKUdatarq=[BLANK]&eqINVdatarq=3&neTYPEdatarq=ant]INV3=5[/REPLACE]This sometimes ignores the neTYPEdatarq arg.When I use this (TYPE field coming first),[REPLACEdb=/DB.db&neTYPEdatarq=ant&neSKUdatarq=[BLANK]&eqINVdatarq=3]INV3=5[/REPLACE]everything 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 x341Internet Coordinator *By e-mail!: michaelw@dhorse.comDark 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:
Sharing DBs across domains (2001)
Greater then less then (2001)
WebCat templates for TyphoonPro admin (1999)
Pass Thru Page? (1998)
Trouble with formula.db (1997)
Re:no [search] with NT (1997)
OT: print landscape (2003)
tag request (1999)
Protect tag for large groups? (1999)
Redirect Possible???????? (2001)
Urgent WebCatalog problem (2000)
newbies to web, spaces in email address (1998)
Problem during evaluation of WebCatalog (1998)
Adding up line items. (2000)
Multiple Items (1998)
Shopping Cart - prices? (1997)
AppleShare IP 6.1 (1998)
[username][password] not showing up! HELP! (1999)
WebDNA Book? (2003)
Foreign Chars (יאצה and so on) (1998)