To: erix,

Nice!!! I had no clue that MySQL syntax can be applied like this.

To be honest out of curriocity I created a small working example:

#!/usr/bin/perl

use strict;
use warnings;
use DBI;

my $username = "username";
my $password = "password";
my $tut_id = "10";
my $tut_title = "title";
my $tut_author = "author";
my $dsn = "dbi:mysql:thanos:127.0.0.1:3306";
my $dbh = DBI->connect($dsn,$username,$password) or die "cannot
connect to database : $DBI::errstr";

my $sth = $dbh->prepare(qq{INSERT INTO `test` VALUES(?,?,?)});

$sth->execute("$tut_id","$tut_title","$tut_author") || die $DBI::errst
+r;

$dbh->disconnect;
[download]

And I am getting this error:

DBD::mysql::st execute failed: Column count doesn't match value count 
+at row 1 at db.pl line 18.
[download]

The moment that I am placing the columns e.g. (`column-1`,`column-2`,`column-3`) the code executes withought any erorrs.

I tried the same syntax on phpMyadmin:

INSERT INTO `test` VALUES ('10','title','author')
[download]

error output:

#1136 - Column count doesn't match value count at row 1
[download]

ERROR 1136 (21S01): Column count doesn't match value count at row 1
[download]

And also at the MySQL (terminal):

ERROR 1136 (21S01): Column count doesn't match value count at row 1
[download]

At this point maybe my version is different.

Well anyway, back to the question. The error should be coming of the avoidance of the quotes on the strings:

Before:

$sth->execute($tut_id,$tut_title,$tut_author) || die $DBI::errstr;
[download]

After:

$sth->execute("$tut_id","$tut_title","$tut_author") || die $DBI::errst
+r;
[download]

Wow so many things that we learn in this forum, I had also no clue about (sqlfiddle). Thanks for sharing. :D

Update:

I think I know the reason that my code withought specifying the columns can not work

From 13.2.5 INSERT Syntax text taken:

If you are not running in strict SQL mode, any column not explicitly given a value is set to its default (explicit or implicit) value. For example, if you specify a column list that does not name all the columns in the table, unnamed columns are set to their default values.

So I assume this syntax can work on SQL but not on MySQL that I am using.

But it was nice that you pointed out, someone who is using SQL will be interested on this.