Why do you need on_conflict_action_MAX when you already haveThis is the central idea of the patch. on_conflict_action_MAX is a marker
ON_CONFLICT_ACTION_DEFAULT?
Anyway, there is no action DEFAULT, it is sooner or later converted to ABORT.
that this field wasn't
initialized yet manually. This allows to detect second attempt to specify
NULL/NOT NULL etc.
There is a comment about this concept in sqlite3AddColumn where
on_conflict_action_MAX is set.
The default behavior is ON_CONFLICT_ACTION_NONE and we have to distinguish
non-initialized
columns and initialized with ON_CONFLICT_ACTION_DEFAULT.
Could we avoid using iPKey in this function? We are going to remove it soon.I don't increase a complexity here and believe that is patch is not about to
suggest a way to exclude iPkey.
No idea.