Upsert with autoincrement 2

These patches fix the bug in which DBAgentSQL3 replace the value in the primary key column with 0 on upsert when AUTO_INCLUREMENT_VALUE(_U64) is used.

Different from MySQL's 'ON DUPLICATE KEY UPDATE', SQLite3's REPLACE once deletes
the duplicated row. So the value in the primary key column is changed. This behavior is not
allowed for our current usage.

Thus I implemented the upsert whose behaivor is similar to MySQL's one.
 
Probably SQLite3 in CentOS6.5 doesn't have these definitions.

However, I suppose that there's no problem if Hatohol runs with
SQLite3 without these definitions.

If NOT NULL constraint happens on INSERT,  the subsequent UPDATE
will also fail due to the same constraint.
As to CHECK constraint, we now don't use it. So we don't have to care it.

Anyway it'd be better to add the above in the comment.