We're just ignoring it right now, so it's probably fine to avoid? Like it doesn't break any existing queries or databases is what I mean.

Ah, I figured that might be the case. Should we perhaps leave a note to clean it up (by just changing the schema directly) just before a release? (I guess I don't have a problem with breaking people using the pre-3.0.0 version for now.)

Well we need to overhaul the schema in general. It worked to get something going, but we need to store account id's and something other stuff i think. I don't remember everything.
Also iirc Eion did some testing and since it's not normalized it gets real big real quick.

Also as we figure out the PurpleHistory GListModel impelementation it's very likely this structure is going to change even more.