fix(sqlite): fix wrongly overwriting storage if empty string#13376
Conversation
Empty string in SQLite3 means anonymous disk-based db, but sequelize overwrited it with :memory: Closes sequelize#13375
|
I get 3 failing tests, but they happen when running |
sdepold
left a comment
There was a problem hiding this comment.
What is the diff between :memory: and anonymous disk-based database?
|
|
So it's still a temporary database that gets deleted after stopping the app, correct? With the only difference that it is either memory or hard drive based. |
|
Seems that all tests are green except for linking. Would you like to have a look and fix it? |
The way I understand it, yes. The use case for a temporary on-disk database is temporary workloads on a memory-constrained machine, like a CI server.
I'm looking in to it. That's odd, because when I ran the linter locally it all passed. |
|
@sdepold All checks passed now. Except 1 skipped check? |
|
Nice one. I'm going to refactor the nullish coalescence refactoring myself in a follow up PR. Thanks a bunch! |
|
🎉 This PR is included in version 6.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…ze#13376) * fix(sqlite): fix wrongly overwriting storage if empty string Empty string in SQLite3 means anonymous disk-based db, but sequelize overwrited it with :memory: Closes sequelize#13375 * fix(sqlite): fix node<10 chokes on nullish coalescing operator * refactor(sqlite): remove unnecessary parentheses around expression Co-authored-by: Sascha Depold <sdepold@users.noreply.github.com>
Empty string in SQLite3 means anonymous disk-based db, but sequelize overwrited it with :memory:
Closes #13375
Pull Request check-list
Please make sure to review and check all of these items:
npm run testornpm run test-DIALECTpass with this change (including linting)?Description of change
Closes #13375