Great content. Actually, if my memory doesn t fail, by that time Informix had a similar database engine (no separate process) ...Informix SE...used it for years and years...there is still software out there using it...just my 5 cents 😊
I have said for years that you know the project is leaving its initial implementation phase when you start removing code. Yes, "NO", is the key scope management tool we all use. But those unexpected points of realization that some code is not needed is a cause for celebration. BTW, that is the only justification for removing tests in my opinion. I was a huge user of Symbian. I had a few of their devices. They, too, were ahead of their time. Richard, I love SQLite. And use it all the time with Python and SqlAlchemy Core. My dbs typically have 2-3 tables. But as you have presented - it is a better file format than the alternatives. For example, I have a budget tracking app that I use multiple times a month. Rollback strategy? I simply roll the db files like one would roll log files (e.g. before importing transactions). It is that simple. And, oops, I have had to use that option to rollback after a bonehead coding mistake. To recover, I fix the coding mistake, unroll the db files, and reprocess. The point is that KISS works well in real life. Thank you!
Great content. Actually, if my memory doesn t fail, by that time Informix had a similar database engine (no separate process) ...Informix SE...used it for years and years...there is still software out there using it...just my 5 cents 😊
I have said for years that you know the project is leaving its initial implementation phase when you start removing code.
Yes, "NO", is the key scope management tool we all use.
But those unexpected points of realization that some code is not needed is a cause for celebration.
BTW, that is the only justification for removing tests in my opinion.
I was a huge user of Symbian. I had a few of their devices. They, too, were ahead of their time.
Richard, I love SQLite. And use it all the time with Python and SqlAlchemy Core. My dbs typically have 2-3 tables. But as you have presented - it is a better file format than the alternatives.
For example, I have a budget tracking app that I use multiple times a month. Rollback strategy? I simply roll the db files like one would roll log files (e.g. before importing transactions). It is that simple. And, oops, I have had to use that option to rollback after a bonehead coding mistake.
To recover, I fix the coding mistake, unroll the db files, and reprocess.
The point is that KISS works well in real life.
Thank you!