-
Notifications
You must be signed in to change notification settings - Fork 152
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 keyv-mysql to the latest version 🚀 #7
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
caseyWebb
pushed a commit
to caseyWebb/keyv
that referenced
this pull request
Oct 10, 2019
caseyWebb
pushed a commit
to caseyWebb/keyv
that referenced
this pull request
Oct 10, 2019
caseyWebb
pushed a commit
to caseyWebb/keyv
that referenced
this pull request
Oct 10, 2019
jaredwray
pushed a commit
that referenced
this pull request
Nov 21, 2021
jaredwray
added a commit
that referenced
this pull request
Nov 21, 2021
* Initial commit * docs(readme): add Greenkeeper badge * Setup entry schema * Use key as primary key * Ensure keys are unique and indexable * Disable timestamps * Add get/set/delete methods * Add clear method * Wait for connection before running queries * Return Boolean for delete method * clear method always resolves to undefined * get method returns undefined on nonexistent keys * Disable logging by default * 0.1.0 * Make invalid connection string more clear * Explicitly use memory for tests * KeyvSQLite => KeyvSqlite * Respect table name * Don't run tests in memory * Accept connection string as contructor argument * Make sure clear only clears current namespace * 0.2.0 * Remove Greenkeeper badge * Test options have expected defaults * Extract keyv-sequelize from keyv-sqlite * Update metadata/readme for Sequelize * Test against SQLite * Set defaults for logging/table * 0.1.0 * Test connection errors are emitted * Extract keyv-sql from keyv-sequelize * Add set method * Add get method * Add delete method * Add clear method * 0.1.0 * Test against SQLite * Ensure keys are unique and indexed as primary keys * Make sure set can update or insert * Use our fork of sql until REPLACE support is merged brianc/node-sql#368 * Keep XO happy * Move back to sql Our changes were merged 🎉 * 0.2.0 * Refactor query into method * Use large busyTimeout with tests Stops 'SQLITE_BUSY: database is locked' errors from creating loads of connections * 0.2.1 * Wrap upserts in if/else so we only run the correct functions Otherwise node-sql will throw errors when building a query that Postgres can't handle * 0.2.2 * Expose opts.dialect rather than sql.dialectName * 0.2.3 * Update to requirable * Lock dependency versions * 0.2.4 * List keyv-postgres and keyv-mysql * 1.0.0 * Fix old Sequelize wording * 1.0.1 * Add keyv logo to header * 1.0.2 * Update sql to the latest version 🚀 (#3) * 1.0.3 * Scope to @keyv * 1.0.4 * Update readme for new scope * 1.0.5 * Update ava to the latest version 🚀 (#7) * Fix JSON quotes in MySQL * 1.0.6 * Allow setting custom VARCHAR key size * Ensure opts.keySize is a number * Test keySize option * 1.1.0 * Add .npmignore * 1.1.1 * Fix bad URLs in package.json (sqlite -> sql) (#10) * 1.1.2 * Update coveralls to the latest version 🚀 (#11) * Update ava to the latest version 🚀 (#12) * Update ava to the latest version 🚀 (#13) * Update ava to the latest version 🚀 (#14) * Update sqlite3 to the latest version 🚀 (#16) * upgrading sqlite3 to version 5.0.2 * creating build yaml for github actions * removing travis ci from build process * updating workflows naming * upgrading pify to version 5.0.0 * updating license to include authors * updating with build status badge * upgrading xo to version 0.45.0 * fixing standard xo issues * fixing standard xo issues * upgrading nyc to version 15.1.0 * upgrading ava to version 3.15.0 * version bump to 1.1.3 * updating authors and github links to jaredwray * updating to include coverage for sql * adding in clean variables and removing rimraf * removing rimraf * removing sqlite * removing sqlite file * moving sql to mono * adding in clean up of sqlite test db * removing from main keyv since importing to mono * validating value coming back Co-authored-by: Luke Childs <lukechilds123@gmail.com> Co-authored-by: greenkeeper[bot] <greenkeeper[bot]@users.noreply.github.com> Co-authored-by: MySidesTheyAreGone <mysidestheyaregone@protonmail.com>
jaredwray
pushed a commit
that referenced
this pull request
Nov 21, 2021
jaredwray
added a commit
that referenced
this pull request
Nov 21, 2021
* Initial commit * docs(readme): add Greenkeeper badge * Setup entry schema * Use key as primary key * Ensure keys are unique and indexable * Disable timestamps * Add get/set/delete methods * Add clear method * Wait for connection before running queries * Return Boolean for delete method * clear method always resolves to undefined * get method returns undefined on nonexistent keys * Disable logging by default * 0.1.0 * Make invalid connection string more clear * Explicitly use memory for tests * KeyvSQLite => KeyvSqlite * Respect table name * Don't run tests in memory * Accept connection string as contructor argument * Make sure clear only clears current namespace * 0.2.0 * Remove Greenkeeper badge * Test options have expected defaults * Extract sequelize logic into subclass * Remove old test * Update keywords * Remove redundant type casting * 0.3.0 * Logging and table are set by default in keyv-sequelize * fix(package): update keyv-sequelize to version 0.1.0 (#3) * Use keyv-sql instead of keyv-sequelize (#5) * 1.0.0 * Pass busyTimeout option to SQLite * Use large busyTimeout with tests Stops 'SQLITE_BUSY: database is locked' errors from creating loads of connections * fix(package): update keyv-sql to version 0.2.0 (#6) * Pin dependency versions * Only accept opts object * 1.1.0 * fix(package): update keyv-sql to version 0.2.3 (#8) Closes #7 * Update to requirable * 1.2.0 * fix(package): update keyv-sql to version 0.2.4 (#9) * 1.2.1 * Finish docs * Also mention table option * fix(package): update keyv-sql to version 1.0.2 (#11) Closes #10 * 1.2.2 * fix(package): update sqlite3 to version 3.1.9 (#13) * 1.2.3 * Update keyv-sql to the latest version 🚀 (#14) * 1.2.4 * Scope to @keyv * 1.2.5 * Use scoped sql package * 1.2.6 * Update ava to the latest version 🚀 (#17) * fix(package): update @keyv/sql to version 1.0.6 (#18) * fix(package): update @keyv/sql to version 1.1.1 (#22) Closes #20 * 1.2.7 * Update @keyv/sql to the latest version 🚀 (#23) * 1.2.8 * Update sqlite3 to the latest version 🚀 (#24) * 1.2.9 * Update sqlite3 to the latest version 🚀 (#25) * 1.2.10 * Update sqlite3 to the latest version 🚀 (#26) * 1.2.11 * Update sqlite3 to the latest version 🚀 (#28) * 1.2.12 * Update coveralls to the latest version 🚀 (#27) * Update ava to the latest version 🚀 (#30) * Update ava to the latest version 🚀 (#31) * Update ava to the latest version 🚀 (#32) * fix(package): update sqlite3 to version 4.0.2 (#40) Closes #34 * Stop testing Node.js v4 and start testing v10 * 2.0.0 * Update sqlite3 to version 4.0.8 (#44) * Update ava to version 1.4.1 (#46) * Update nyc to version 14.1.1 (#48) Closes #36 * 2.0.1 * Update sqlite3 and don't pin version * 2.0.2 * upgrading travisci to node version 12,14, and 16 * adding github build tests * updating to just run tests * updating build name * removing travisci * adding github status badge for build to readme * upgrading pify to version 5.0.0 * upgrading sqlite3 to version 5.0.2 Thanks to @jdesboeufs for this work. * upgrading ava to 3.15.0 * upgrading nyc to version 15.1.0 * upgrading to xo version 0.45.0 * xo clean up opts renamed to options err renamed to error tabs and spaces * moving the busy timeout to 3 seconds * maintenance release and version bump to v.2.0.3 * moving to standard test suite * adding in nvm for support on 16 * updating licensing to include authors * Delete yarn.lock * no longer needed in mono repo * import into mono repo * adding in code coverage for sqlite * removing this as a storage adapter in keyv Co-authored-by: Luke Childs <lukechilds123@gmail.com> Co-authored-by: greenkeeper[bot] <greenkeeper[bot]@users.noreply.github.com> Co-authored-by: Aditya Patadia <adityapatadia@users.noreply.github.com>
jaredwray
pushed a commit
that referenced
this pull request
Nov 22, 2021
jaredwray
added a commit
that referenced
this pull request
Nov 22, 2021
* Initial commit * docs(readme): add Greenkeeper badge * Create Travis DB for tests * Use pq@6 pq@7 appears to have issues with Sequelize * 0.1.0 * Keyvpostgres => KeyvPostgres * Remove Greenkeeper badge * Use keyv-sql instead of keyv-sequelize * Format pq query results as array of rows for keyv-sql * Don't use obj destructuring for Node.js 4 compat * Remove sequelize dependencies * Update to keyv-sql 0.2.3 for latest Postgres compat * Test against Postgres 9.5 on Travis * Lock dependency versions * Only accept opts object as constructor argument * 1.0.0 * requireable => requirable * 1.0.1 * fix(package): update keyv-sql to version 0.2.4 (#4) * 1.0.2 * Finish docs * Update keyv-sql to the latest version 🚀 (#5) * 1.0.3 * fix(package): update keyv-sql to version 1.0.2 (#6) Closes #5 * 1.0.4 * Update pg to the latest version 🚀 (#7) * 1.0.5 * Update keyv-sql to the latest version 🚀 (#8) * 1.0.6 * Scope to @keyv * 1.0.7 * Import scoped test suite * 1.0.8 * Update pg to the latest version 🚀 (#11) * 1.0.9 * Update pg to the latest version 🚀 (#12) * 1.0.10 * Update ava to the latest version 🚀 (#13) * fix(package): update @keyv/sql to version 1.0.6 (#14) * fix(package): update pg to version 7.2.0 (#15) * 1.0.11 * Update pg to the latest version 🚀 (#17) * 1.0.12 * Update @keyv/sql to the latest version 🚀 (#18) * Update @keyv/sql to the latest version 🚀 (#19) * 1.0.13 * fix(package): update @keyv/sql to version 1.1.2 (#20) * 1.0.14 * Update coveralls to the latest version 🚀 (#21) * Update ava to the latest version 🚀 (#22) * Update pg to the latest version 🚀 (#23) * 1.0.15 * Update ava to the latest version 🚀 (#24) * Update pg to the latest version 🚀 (#25) * 1.0.16 * Update package.json Old versions of pg don't work with new versions of node.js (14+) * moving github actions to build * moving to local postgres * updating to create the database * creating database * set the user password * updating command formatting * updating postgres password * same user and pass * user and pass the same * updating to handle xo upgrade * updating to handle new format with xo * upgrading nyc to latest version 15.1.0 * removing travis ci as no longer needed * updated build status badge on readme * upgrade xo to version 0.45.0 * fix options to be named correctly * upgrading ava to version 3.15.0 * moving testing to staged * fixing tests * updating to just Official Tests * Update test.js * adding in api tests * adding in value tests * moving build to 1 parallel process * update to stop and start the service * trying createdb * trying create db * adding in owner * adding in multiple stores * version bump for release v1.0.17 * updated for serial flag on ava * updated tests to more uniform * adding in docker compose for testing * adding in docker compose for build * adding in docker compose via scripts * updating to use npm run * moving to latest version of postgres * correcting flow of build * moved docker compose to test folder * changed naming convention to be more uniform * updating for new npm run command to start postgres * updated compose to test folder and removed values * updated readme around how to test * naming adjusted * updating for testing * Update README.md * updating licensing for all authors * adding nvm and also removing yarn to standardize on npm * upgrading xo to version 0.46.4 * updating build to reference correct testing * upgrading @keyv/sql to version 1.1.3 * adding codecov on build workflow * removing codecoverage output from project * remving coveralls * updating badge * updating to run coverage * version bump to v1.0.18 * no longer needed * import @keyv/postgres to mono repo Co-authored-by: Luke Childs <lukechilds123@gmail.com> Co-authored-by: greenkeeper[bot] <greenkeeper[bot]@users.noreply.github.com> Co-authored-by: Andrey Frimuchkov <afrimuchkov@yandex.ru>
jaredwray
pushed a commit
that referenced
this pull request
Oct 28, 2022
* Update index.md Created a Getting Started Guide * Getting Started Guide Updates made basted on feedback from Jared. * Getting Started Guide Added Sections 6 and 7 Compression and Caching * Getting Started Added example to #3. * Getting Started Guide Updated example * Getting Started Guide Updated the title of #7
jaredwray
pushed a commit
that referenced
this pull request
Nov 3, 2022
* Update index.md Created a Getting Started Guide * Getting Started Guide Updates made basted on feedback from Jared. * Getting Started Guide Added Sections 6 and 7 Compression and Caching * Getting Started Added example to #3. * Getting Started Guide Updated example * Getting Started Guide Updated the title of #7 * Create caching-javascript.md Added How to implement Caching with Javascript page * Create caching-node.md Added caching-node.md file - How to Implement Caching in Node, same as How to Implement Caching in Javascript
jaredwray
added a commit
that referenced
this pull request
Nov 9, 2022
* Update index.md Created a Getting Started Guide * Getting Started Guide Updates made basted on feedback from Jared. * Getting Started Guide Added Sections 6 and 7 Compression and Caching * Getting Started Added example to #3. * Getting Started Guide Updated example * Getting Started Guide Updated the title of #7 * Create caching-javascript.md Added How to implement Caching with Javascript page * Create caching-node.md Added caching-node.md file - How to Implement Caching in Node, same as How to Implement Caching in Javascript * Caching pages Added SEO for Express, Fastify, Koa, NestJS and Node. Code sample also added to the Express page Co-authored-by: Jared Wray <me@jaredwray.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 0.2.1 of keyv-mysql just got published.
The version 0.2.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of keyv-mysql.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 2 commits.
5a43877
0.2.1
da81fe9
fix(package): update keyv-sql to version 0.2.4 (#4)
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴