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.
 
> However, this is also an convenient point, isn't it.

Really!? I don't think so because we don't have any use case for it yet.
If we have some use cases, I may consider it is an convenient point. But I think that it is a trap rather than an convenient point for now.



> Anyway, I'll think these things as another topic.

I agree with you.