As an aside (yes, I know the SQL is missing a FROM
clause) that particular SQL statement is not really that
long. Once you start programming a bit more, SQL
statements 10x as long as that can become the norm. I highly
recommend you start developing a better style to handle
the SQL (for aesthetic, as well as other reasons). Try
putting the SQL in a variable and then stick that
variable into the prepare, like this:
my $CONTACT_SQL = "
SELECT C.forename, C.surname, B.occupation, A.position, C.city,
C.country AS forename, surname, occupation, position, city, cou
+ntry
FROM ACN A, BUSINESS B, CONTACTS C
WHERE C.ruid=B.ruid
AND C.ruid=A.ruid
AND forename LIKE ?
AND surname LIKE ?
AND occupation LIKE ?
AND position LIKE ?
AND city LIKE ?
AND country LIKE ?";
my $sthQuery = $dbh->prepare($CONTACT_SQL)
or die "Couldn't prepare query: $DBI::errstr";
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.