I agree that this is very strange behavior, perhaps to be considered a bug. With SQLite v3.33.0, I get a different error message from the same input:<code> there is already an index named i1 </code>
I agree that this is very strange behavior, perhaps to be considered a bug. With SQLite v3.33.0, I get a different error message from the same input:<code> there is already an index named i1 </code>