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:
session handling (2004)
Banners (1997)
nesting limits? (1998)
Search crashing server (1998)
OT Pager notification of completed orders (1998)
Auto SKU's (2000)
Calendar (1997)
Re:2nd WebCatalog2 Feature Request (1996)
[WebDNA] after latest OSX upgrade, WebDNA not running? (2011)
2.0 Info (1997)
Entry pages (was: WebCatalog MAJOR drawback) (1998)
emailer (1997)
Multiple appends with checkboxes (1998)
$Replace with [founditems] (1997)
E-Commerce site for Canadian and US customers (1998)
WebMerchant and PCAuthorize (1998)
Re:Subject: Mail Server Software (1998)
A few questions. . . (1997)
Been meaning to ask... (1997)
[WebDNA] [OT] Phone solution for multiple companies at same location (2010)