Re^2: DBI variable argument count

oh my. I don't get it. I think I'm doing this right but I'm obviously not.

$request = "SELECT * FROM nsmw WHERE unit = ? AND name1 REGEXP ? AND e
+mail REGEXP ? ORDER BY unit"

@values = ("001", "duckman", "google.com");

# Do database transaction
my $dbh = DBI->connect("DBI:mysql:database=db;host=localhost", "user",
+ "user",{'RaiseError' => 1});
my $sth = $dbh->prepare($request);
$sth->execute(@values);

while (my $ref = $sth->fetchrow_hashref())
{
    # here is where the magic happens
    h3("Unit $ref->{'unit'}");
}
[download]

There is a matching row in that DB but for some reason it just doesn't print anything in the while loop. :(

I think maybe I'm just too tired. I've been coding for 9 hours without a break =)

Comment on Re^2: DBI variable argument count Download Code

Replies are listed 'Best First'.
Re^3: DBI variable argument count by ig (Vicar) on Sep 14, 2012 at 02:50 UTC
Take a break - it's amazing what a fresh mind can see. I'm not familiar with REGEXP, so can't comment on that. I would strip down the query then build it back up one argument at a time, to see where the problem is. Do you get some records from the query `select * from nsmw`? If so, then add your where clauses one at a time. This will, at least, narrow your focus a bit. update: a quick look at REGEXP turns up this for MySQL 5.1: The REGEXP and RLIKE operators work in byte-wise fashion, so they are not multi-byte safe and may produce unexpected results with multi-byte character sets. In addition, these operators compare characters by their byte values and accented characters may not compare as equal even if a given collation treats them as equal. Are your strings plain ASCII or are they multi-byte?	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: DBI variable argument count
by ig (Vicar) on Sep 14, 2012 at 02:50 UTC

Take a break - it's amazing what a fresh mind can see.

I'm not familiar with REGEXP, so can't comment on that.

I would strip down the query then build it back up one argument at a time, to see where the problem is. Do you get some records from the query select * from nsmw? If so, then add your where clauses one at a time. This will, at least, narrow your focus a bit.

update: a quick look at REGEXP turns up this for MySQL 5.1:

The REGEXP and RLIKE operators work in byte-wise fashion, so they are not multi-byte safe and may produce unexpected results with multi-byte character sets. In addition, these operators compare characters by their byte values and accented characters may not compare as equal even if a given collation treats them as equal.

Are your strings plain ASCII or are they multi-byte?

[reply]
[d/l]