The returned values should be exact. As far as how much data, I'm assuming your talking about amount of records ? Potentially eventually maybe quite a bit. Currently mysql statement is comprised of select and from with all the proper joins. But I"m confused, when you say below actual SQL call here, is the referring to the SQL statement that would look at all the imput values and process the data ? like a series of and's or or's ?
Stuart --- gerald_clark <[EMAIL PROTECTED]> wrote: > Depending on how exact the returned values need to > be, and how much data > you have to > sift through, you could do. ( perl example ) > $job=$dbh->quote($job.'%'); > $city=$dbh->quote($city.'%'); > $start=$dbh->quote($start.'%"); > . > . > . > > $select = "SELECT * from myfile where jobtitle like > $job and city like > $city and start like $start and industry like > $industry and state like > $state and taxterm like $taxterm"; > . > . > do the actual SQL call here. > > Stuart Felenstein wrote: > > >I'm back, trying to figure my way through a > somewhat > >confusing set of conditons. > >Sort of doing a sanity check here. > >First explanation: > >I've put together a search (the database) form that > >has 6 inputs. > >Just to clarify, the fields are > >1-JobTitle > >2-City > >3-Start > >4-Industry > >5-State > >6-TaxTerm. > > > >The idea is that a user can choose one , two or all > >fields to put criteria into. Regardless, whichever > >one they choose , there should be a records return. > > >More criteria of course adds more refinement. > > > > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
