[malcolmd3111]

I need to modify some records in a MySQL table. The defined field contains text. My syntax (in Perl) is as follows:

$statement = "UPDATE tblgenjnl SET printview='$prv_row' WHERE record='$row[0]' ";

tblgenjnl is the Table
printview is the field to be updated
$prv_row is the new content
record is the record number
$row[0] is the retrieved value from the table of required record.

The program runs, but there is something wrong with this command syntax. Any help woould be appreciated.

Thanks,

Malcolm3111

[RGregory]

Not familiar with Perl, but if record is a variable, shouldn't it be outside of the quotes as in...

$statement = "UPDATE tblgenjnl SET printview='$prv_row' WHERE '#record'='$row[0]' ";

[cristobal03]

That shouldn't be a problem with perl, which interpolates variables in strings (that was my first instinct as well, but I'm pretty confident that isn't the issue).

Saying "there is something wrong with this command syntax" is somewhat ambiguous. Is the code generating errors? Is there an unacceptable pattern to the queries? Can't you print a log of the strings to see what's actually being sent to the MySql engine?

I guess I mean, what behavior are you seeing to suggest it's problem code?

chris.

[cristobal03]

[bump]

Though, actually, now, let's see...it's been a while since I've used perl...RGregory may have it.

I believe it is the single quotes that are causing the trouble. Single quotes in perl indicate literal strings, I believe, so those variables $prv_row and $row[0] are not being interpolated into the string.

You might have to use ASCII/ANSI character functions to generate the single-quotes. Or escape them using a backslash (I think that's perl's escape character, anyway).

HTH

chris.

[malcolmd3111]

Thanks for the replies. I evaluated my sql expression again and found the problem. The correct syntax is shown below:

'UPDATE tblgenjnl SET printview="$prv_row" WHERE record="$row[0]"')

Unlike Perl which uses "" to evaluate an expression, rather than ' ' (single quotes) MySQL requires the double quotes to stop a var being evaluated. In the statement above the variable $prv_row is free form text containing MySQL reserved words. Using single quotes the MySQL parser evaluates the contents, with double quotes it does not.

This all began because of the incompatibilities between FileMakerPro and MySQL regarding new line chars.

Peace