I really miss strict, warnings, taint mode, and RaiseError.
Interpolating variables into SQL statements usually triggers my "use placeholders" warning (Re: Counting rows Sqlite, Re^2: Massive Memory Leak). But in the only SQL statement you show here, you "just" interpolate a constant table name into the SQL statement. Not as bad as variable data from the network, but still, you should use DBI's quote_identifier() method. That won't even break when you change $DbUsers.
More:
X:\>perl 1199050.pl syntax error at 1199050.pl line 26, near ""$DBI::errstr":" syntax error at 1199050.pl line 34, near "}" Execution of 1199050.pl aborted due to compilation errors. X:\>
Better copy&paste from the actual source. Manual typing adds extra errors.
Alexander
In reply to Re^3: DBD DBI Mysql Connect
by afoken
in thread DBD DBI Mysql Connect
by Umdurman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |