2011/05/14 21:47 +0200, misiaq
You're right about explain. That is why I suggested to use explain EXTENDED and
then SHOW WARNINGS.
Second query will show you the optimizer output. As far as I understand - that
was the par of your question.
Yes, I did that. That output showed no
since your listing the columns, you could just leave off `idlog` from
the named columns and thus not also need to include the null in the
inserted values.
INSERT INTO `friendlyCMS`.`log`
(`imepriimek`, `clock`, `action`, `onfile`, `filesize`)
VALUES ($_COOKIE['user'], CURRENT_TIMESTAMP, 'saved'
If you're asking what I think you're asking, then yes, both NULL and 0 will
trigger an autoincrement field to put in the next value.
- Original Message -
> From: "Grega Leskovšek"
> To: mysql@lists.mysql.com
> Sent: Monday, 16 May, 2011 4:49:43 PM
> Subject: [setting value when INSERT fo
Should it be null?
INSERT INTO `friendlyCMS`.`log` (`idlog`, `imepriimek`, `clock`,
`action`, `onfile`, `filesize`) VALUES (NULL, $_COOKIE['user'],
CURRENT_TIMESTAMP, 'saved',$filename, filesize($filename));
idlog is primaryk ey auto inrement not null...
When insertin the value what should I pass i
