Unable to automatically insert auto_increment values

Hi there,

I don`t really understand the problem.

I tested the following table:

DROP TABLE IF EXISTS `mazzo`;
CREATE TABLE IF NOT EXISTS `mazzo` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `idgiocatore` int(11) NOT NULL,
  `idcarta` int(11) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;

I can no execute the following queries:

INSERT INTO `mazzo` (`id`, `idgiocatore`, `idcarta`) VALUES
 ('', '', '');

INSERT INTO `mazzo` (`id`, `idgiocatore`, `idcarta`) VALUES
 (null, '', '');

INSERT INTO `mazzo` (`idgiocatore`, `idcarta`) VALUES
 ('', '');

In all of these cases I get a new row with a new auto_increment value, so everything is ok?

Hi David,

it themes to me, that you've mysqls strict mode not enabled. If I run your example I get mysql error #1366, because '' is not a valid integer value.

Disabling mysqls strict mode is absolutely no option in production. None of your examples should work in a productiv environment. A valid query for your table definition should look like this:

INSERT INTO `mazzo` (`id`, `idgiocatore`, `idcarta`) VALUES
 (null, 0, 0);

Hi Sebastian,

ahh, now it makes sense, thanks for pointing that out.
Yes, I don`t have mysql`s strict mode enabled on my dev machine so this is why I could not reproduce it.
And of course you are right, we should really create valid sql on the insert tab.

So I will change the title of this report to something like this: Unable to automatically insert auto_increment values on "Insert-Tab" when in mysql_strict_mode. Do you agree?

Hi again,

yes of course I agree.

This bug is the only thing that stops me from using chive in our company for production. It would be great if that's getting fixed in future. Thx in advance.

Fixed in trunk. Thanks for the report.