Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sqlite{,-analyzer}: 3.28.0 -> 3.29.0 #65402

Closed
wants to merge 1 commit into from

Conversation

dtzWill
Copy link
Member

@dtzWill dtzWill commented Jul 26, 2019

Motivation for this change

https://www.sqlite.org/releaselog/3_29_0.html

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@dtzWill
Copy link
Member Author

dtzWill commented Jul 26, 2019

perl's dbd sqlite will probably need updating, there's activity so hopefully it's available soon?

https://github.com/DBD-SQLite/DBD-SQLite/releases

@@ -41,6 +41,9 @@ stdenv.mkDerivation rec {
"-DSQLITE_SECURE_DELETE"
"-DSQLITE_MAX_VARIABLE_NUMBER=250000"
"-DSQLITE_MAX_EXPR_DEPTH=10000"
# Release notes for 3.29.0 say this is recommended
# https://www.sqlite.org/compile.html#rcmd
"-DSQLITE_DQS=0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder about the comment here (should go into the commit message rather) since our settings don't follow all the recommendations, for instance they recommnad DSQLITE_MAX_EXPR_DEPTH=0 Shouldn't we update others as well ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question, the reasoning for these particular settings (where deviating from upstream) is unknown :/. Perhaps answers could be found with some git history spelunking but even better would be if we documented the purpose/scope/validation-still-needed (perhaps these parameters help one guy's use case but are terrible for other folks'? who can say....).

In short I suppose we should push the technical debt further down the road and leave the options as-is? :(

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we change it then better early than right before the release.
SQLITE_MAX_VARIABLE_NUMBER and SQLITE_MAX_EXPR_DEPTH can be explained via #36293 .
As for other recommended defaults. Maybe we could just add them one by one across updates in order not to break too many things ?

@dtzWill
Copy link
Member Author

dtzWill commented Oct 7, 2019

Well we're behind 2 revs now. 3.30 came out.

@d-goldin
Copy link
Contributor

This PR should be closed or the good parts picked and updated, as 3.30 went into master in #70593 (comment)

@dtzWill
Copy link
Member Author

dtzWill commented Oct 22, 2019

Thanks all, @teto and @d-goldin ! Sorry for not seeing this through, closing since seems like at least the version portion made it in. If anyone thinks it's worth addressing the issue discussed above re:justifying our config choices (esp those conflicting with sqlite's recommendations and/or other distro builds) please speak up -- even if collectively folks don't have gusto to tackle it just yet :). Otherwise let's hope those commits were made with wisdom and hope for the best....

@dtzWill dtzWill closed this Oct 22, 2019
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.

None yet

3 participants