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:
no global [username] or [password] displayed ... (1997)
[WebDNA] checking for mixed case text (2009)
PCS Customer submissions ? (1997)
Web Developer Product Awards (1997)
Encyption mail was Suggestions for Topics ... (1998)
WCS Newbie question (1997)
Erotic Sites (1997)
how to set a new cart number periodically (1999)
4.5.0 (2002)
japanese characters (1997)
Limit to variables passed on to next tpl? (1998)
(2000)
apostrophe in search item (1997)
Hiding my Source Code with W* (2000)
Multiple shipping databases (1997)
Text data with spaces in them... (1997)
New One (for me).... Error type 12 (1999)
WebCat2.0 [format thousands .0f] no go (1997)
SET (1998)
WCf2 and nested tags (1997)