I know about SQLite's 'problem' when inserting/updating many rows, but that's not the case here.

I'm updating ONE field in ONE row, indexed by PK, in a table with ~ 250 records. The query always takes ~ 200 ms. That sounds like very little, but it's huge.

Why does 1 very simple `UPDATE` query take 200 ms?? All reads are blazing fast.

I've tried:

* `BEGIN` and `COMMIT` -- no change, because it's just 1 statement
* `PRAGMA journal_mode=PERSIST` -- no change, apparently disk io isn't the problem?
* removing the `UPDATE` statement -- that works wonderfully for time!, but it's not very persistent

To compare to MySQL on the same system: **0.6ms** in a very similar database.

I don't need transactional security (ACID?) or whatever you call that. If the computer crashes during this query, I'm fine with losing **all** changes. MySQL (InnoDB) has an option for this: `innodb_flush_log_at_trx_commit`. Does SQLite have something like that?

I'm using sqlite-3.7.9, if that matters.