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

Update dependency better-sqlite3 to v7 #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 29, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
better-sqlite3 ^5.0.0 -> ^7.0.0 age adoption passing confidence

Release Notes

JoshuaWise/better-sqlite3

v7.5.0

Compare Source

  • Upgraded SQLite to version 3.37.2
  • added the .busy property to prepared Statements
  • added the nativeBinding option to the Database constructor
  • changed the code property of SqliteError to be enumerable
  • added SqliteError to the API documentation
  • Removed tar dependency
  • Reduced the size of installing better-sqlite3 (by using a files list in package.json)

v7.4.6

Compare Source

What's Changed

  • Upgraded to SQLite version 3.37.0

New Contributors

Full Changelog: WiseLibs/better-sqlite3@v7.4.5...v7.4.6

v7.4.5

Compare Source

What's Changed

New Contributors

Full Changelog: WiseLibs/better-sqlite3@v7.4.4...v7.4.5

v7.4.4

Compare Source

  • ~added prebuilds for Alpine containers~ (looks like this failed)
  • added prebuilds for Windows 32-bit
  • fixed various installation issues

v7.4.3

Compare Source

Fixed WiseLibs/better-sqlite3#651

v7.4.2

Compare Source

  • Upgraded SQLite to version 3.36.0
  • Added SQLITE_ENABLE_MATH_FUNCTIONS compile-time option

v7.4.1

Compare Source

  • Fixed some installation issues
  • Added prebuilt binaries for Node v16
  • Added prebuilt binaries for Electron v13

v7.4.0

Compare Source

v7.3.1

Compare Source

v7.3.0

Compare Source

  • Added the db.serialize() method.
  • Buffers returned from db.serialize() can be opened as in-memory databases by passing them to new Database(buffer).
  • Added the stmt.readonly property.
  • added the directOnly option to user-defined functions and aggregates.

v7.2.0

Compare Source

  • added support for the RETURNING clause
  • statements that return data can now be executed via .run() if no query results are desired

v7.1.5

Compare Source

  • Fixed subclassing (e.g., class MyClass extends Database {})

v7.1.4

Compare Source

  • Fixes for Jest environments
  • Updated SQLite to v3.35.2

v7.1.2

Compare Source

v7.1.1

Compare Source

v7.1.0

Compare Source

Updated SQLite to version 3.32.0.

v7.0.1

Compare Source

v7.0.0

Compare Source

Breaking changes

Non-breaking changes

  • Added support for worker threads (see an example here)
  • Added support for Jest environments
  • Fixed many issues related to users building packaged executables, including:
    • FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal
    • FATAL ERROR: v8::Object::GetAlignedPointerFromInternalField()
    • Error: Cannot find module '...\node_modules\integer\node
    • Various electron-related issues
  • Added an optional second parameter to db.loadExtension() which allows users to specify the entry point of the extension
  • Improved documentation for building custom configurations
  • Documented some undocumented features.
  • Enabled SQLITE_ENABLE_GEOPOLY
  • Enabled SQLITE_THREADSAFE=2
  • Enabled SQLITE_OMIT_SHARED_CACHE
  • Removed SQLITE_USE_URI
  • The "verbose" option now logs SQL passed to db.exec() in statement-by-statement fashion, rather than all at once (to match the behavior of using prepared statements)
  • Added "unsafe mode" which allows advanced users to do dangerous things at their own risk:
    • allows users to mutate the database while iterating through a query, which has non-deterministic behavior
    • disables SQLITE_DBCONFIG_DEFENSIVE which allows users to corrupt their database file and execute undefined behavior

v6.0.1

Compare Source

v6.0.0

Compare Source

Breaking changes

Non-breaking changes

  • Updated SQLite to version 3.31.1.
  • Fixed many installation bugs.
  • Added support for prebuilt binaries.
    • Prebuilt binaries are available for this version, and will be available for all subsequent versions. The binaries are built by prebuild whenever a new release tag is made in github, via a travis CI workflow. As you can see in the travis config file, prebuild currently builds binaries for Node 8, 10, and 12, and Electron 2, 3, 4, 5, 6, and 7. Non-LTS node versions are not supported, but compiling better-sqlite3 from source should still work fine for those versions, as it always had. Prebuilt binaries are only made for Linux and Mac OSX, not Windows (but again, building from source should work fine on Windows too).

v5.4.3

Compare Source

v5.4.2

Compare Source

v5.4.1

Compare Source

v5.4.0

Compare Source

  • Added support for online backups via the db.backup() method.
  • Added verbose mode, which allows you to log all SQL executed by a database connection.
  • You can now execute read-only SQL while retrieving data via stmt.iterate().
    • Previously, you would get a "database connection is busy" error.
    • This allows you to perform nested calls to stmt.iterate().
  • Removed the SQLITE_OMIT_TRACE compilation option.
  • Enabled the SQLITE_TRACE_SIZE_LIMIT=32 compilation option.

v5.3.0

Compare Source

v5.2.1

Compare Source

v5.2.0

Compare Source


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

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.

Cannot insert empty buffer (it becomes NULL)
1 participant