There are a few suggestions I'd make here. The first is to make your code a little *less* paranoid about newlines. You control all the form input already, so those chomps aren't going to do anything. The *only* place where you're going to potentially have extra newlines is on the end of each line, i.e. at the end of $record[6]. Just chomp each line as you read it in, and you can leave the rest. Since the DB and the CGI are running on the same OS, they should have the same "concept" of a newline. One trick you can use to find out if there are lingering characters is to print out the value within delimiters, i.e. print "<p>color is '$color'</p>\n";, so if it is a newline problem you can track it down a little quicker.

Which reminds me, for ($record[6]) { s/\r\n//; } is an *odd* piece of code -- you're not iterating over anything. Just do $record[6] =~ tr/\r\n//d; instead (if chomping doesn't help).

More importantly, I'd suggest using a different logic to generate matches. That if is long and hard to maintain. But that would take a lot of thought and effort, and it's rather late in the day.

HTH! 

perl -e 'print "How sweet does a rose smell? "; chomp ($n = <STDIN>); 
+$rose = "smells sweet to degree $n"; *other_name = *rose; print "$oth
+er_name\n"'

[download]

In reply to Re: Adding features to a CGI search engine by arturo
in thread Adding features to a CGI search engine by wiz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.