Interesting, today I realized we have a "OPTIMIZED" column option, but it's not used anywhere. The comment in the code says that it should mean that the table logic can filter down the results more efficiently than sqlite, given a specific column value, but to not expect it to behave like an index (because it's not an indicator that the row is unique). Do we know why it's not implemented/ used anymore? The only thing I see it's used in is to say that the table is non cacheable if a column with that option exists.