Skip to content

updated SQLite to 3.8.9 from 3.8.5#14

Closed
ariccio wants to merge 1 commit intonotepad-plus-plus:masterfrom
ariccio:update-sqlite
Closed

updated SQLite to 3.8.9 from 3.8.5#14
ariccio wants to merge 1 commit intonotepad-plus-plus:masterfrom
ariccio:update-sqlite

Conversation

@ariccio
Copy link
Contributor

@ariccio ariccio commented May 4, 2015

downloaded, extracted, and replaced old version with files from SQLite 3.8.9 (released April 8th, 2015)

...hence the changeset _looks_ huge, but I, personally, didn't change a single line.

downloaded, extracted, and replaced old version with files from SQLite
3.8.9 (released April 8th, 2015)

...hence the changeset looks huge, but I personally didn't change a
single line.
@donho
Copy link
Member

donho commented May 5, 2015

Thank you for the update... but what is the reason of this update?

@ariccio
Copy link
Contributor Author

ariccio commented May 5, 2015

I'm not sure that I understand your question?

This is a regularly scheduled maintenance release.

@MAPJe71
Copy link
Contributor

MAPJe71 commented May 6, 2015

Don't fix it when it ain't broken.

@ariccio
Copy link
Contributor Author

ariccio commented May 6, 2015

  • There are a bunch of improved debugging/reliability features (e.g. SQLITE_ENABLE_API_ARMOR), and many small bugfixes. One bug was encountered by "a prominent SQLite user", and was serious enough to justify a rushed fix.
  • This is not a breaking change, if the behavior of Notepad++ changes in any (negative) way, then Notepad++ is broken, _by definition_.

@donho
Copy link
Member

donho commented May 6, 2015

Notepad++ use a small part of functionalities of SQLite. While there is no bug on this part so far, I don't see any reason to take the risk having regression to update whole SQLite.

@donho donho closed this May 6, 2015
@ariccio
Copy link
Contributor Author

ariccio commented May 6, 2015

Grr. Ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants