afterConnect hook doesn't work with SQLite

[bradisbell]

Issue Description

What are you doing?

Attempting to register an afterConnect() hook.

const Sequelize = require('sequelize');

const sequelize = new Sequelize({
  dialect: 'sqlite',
  storage: 'db.sqlite',
});

sequelize.afterConnect(async (connection, config) => {
  console.log('HOOK CALLED'); // <<< Never happens
  connection.query('PRAGMA journal_mode=WAL;');
});

sequelize.authenticate().then(/* model setup, etc. here */);

What do you expect to happen?

I expected the hook to be called.

What is actually happening?

The hook simply never gets called. No error occurs when the hook is registered.

Environment

• Sequelize version: 5.21.2
• Node.js version: 12.11.1
• Operating System: Windows 10 x64

Issue Template Checklist

How does this problem relate to dialects?

• I think this problem happens regardless of the dialect.
• I think this problem happens only for the following dialect(s):
• I don't know, I was using sqlite, with connector library version 5.0.0 and database version XXX

Would you be willing to resolve this issue by submitting a Pull Request?

• Yes, I have the time and I know how to start.
• Yes, I have the time but I don't know how to start, I would need guidance.
• No, I don't have the time, although I believe I could do it if I had the time...
• No, I don't have the time and I wouldn't even know how to start.

[github-actions]

This issue has been automatically marked as stale because it has been open for 7 days without activity. It will be closed if no further activity occurs. If this is still an issue, just leave a comment or remove the "stale" label. 🙂

[bradisbell]

Not stale.

[nlwillia]

We were trying to setup migrations for in-memory sqlite tests and couldn't figure out why the hooks weren't working. 😩 It would be great to see this fixed.

[WikiRik]

It seems that there was a PR that could solve this issue. I'll see if I can patch that one up and get it working with the current version next week

[msbsh]

@WikiRik any updates?

[megahypercat]

We really need support for performance optimizations with sequelize. This is one of them.
It's really unfortunate when you build something but as it grows, sequelize becomes a major performance bottleneck.