Re:The lack of proper “alter table” support in SQLite
by PommeDeTerre on Sunday June 16, 2013 @08:07AM
(#5888205)
But now every user of SQLite needs to deal with a library that's larger, and includes non-critical functionality that goes unused.
The whole point of using SQLite in the first place is to avoid such overhead, knowing full well that some non-essential functionality is being lost as part of this tradeoff.
I think it's far more important to keep SQLite small and nimble for the many users who are facing constraints beyond their control (imposed by limited hardware resources, for instance), rather than bloating it for the sake of a small number of users who are unwilling (or too lazy?) to write proper manual migration scripts now and then.
Re:The lack of proper “alter table” support in SQLite
by rogerbinns on Sunday June 16, 2013 @11:04AM
(#5888652)
SQLite make it clear when you could use it: http://www.sqlite.org/whentouse.html
It is okay not use SQLite, and no one will be upset if a different database is used. Every source file starts with a blessing!
Yes because now every SQL migration library of every language has its own partial bug-ridden of a full alter table for sqlite. That does sound so much better than having a single implementation in sqlite itself (wait no, it does not even remotely).