On Fri, 26 Feb 2016 at 16:42 Simon Slavin <slavins at bigfraud.org> wrote:
> > I thought I knew where it was documented but I can't find it at the > moment. The idea is that if you have given the column an explicit name (in > your case 'storeID') then you might be referring to it in your code, so > SQLite shouldn't change the values. > > That should work correctly in the current and all future versions of > SQLite3. It's an assumption lots of programmers make. > My question is whether modifying "sqlite_master" after the fact to make the schema like this has any possible pitfalls/caveats, as opposed to creating the table this way from the start. It's not really clear to me how to tell what schema modifications are sound and what are not (eg. if you add the column to the beginning of the schema instead of the end, the table gets corrupted because now all of the columns are offset 1 from how they're actually stored).
