connection_pool | Generic connection pooling for Ruby

Try to remove explicitly adding _id to schema with value of mongoose.Types.ObjectId(). Remove these lines from schema definition.

$set will replace a new value for the key. If you use the 3rd value then the $set will replace the 3rd value, use $push instead of $set operator.https://docs.mongodb.com/manual/reference/operator/update/push/

The solution is only to add a check in your handler, like so:

Use the below SQL statement:

First confirm that TCP is enabled, else try to enable it with the below steps

1. Open SQL Server Configuration Manager
2. Expand “SQL Server Network Configuration” and click on “Protocols for MSSQLSERVER”
3. Right click on “TCP/IP” and choose “Enable”
4. Click “OK” on the Warning that the service will have to be restarted
5. Click on “SQL Server Services”
6. Right click on “SQL Server (MSSQLSERVER) and choose “Restart”

Confirm your jdbc driver path below and specify it in the connection too

I have my code below and works as is. A few things:

1. Install dependencies again if needed
2. I am using the sample airbnb db they provide in Atlas service on cloud.mongodb.com
3. Change username:0987654321 to your own username and password where 'username' is the username and 0987654321 is the password.
4. Run() works fine locally but it's not straight forward to have a local method start a server endpoint and keep track of it or vice versa. For that you need good chaining

So only USE the run method to test locally and it works fine or use the express endpoints to test via your app client side or curl or postman and that works too independently.

Heres my whole server file:

A materialized view is not a bad solution, but only if you can regard it as "point in time" (beginning of business day, or within last 3 hours, ...). It is not a good solution for an "at this moment" requirement. Yours seems to be the latter.
Your best option would be just creating a view that gets the latest data. If that is not viable, due to audit event size, then need to look elsewhere. I am not a fan of creating a table to contains the latest data. That would be replicating the data, and replicated data inevitability winds up being different. But a slight twist comes to mind: Create a table that contains only the event id and the event_audit log id, maintaining only the last audit id. Without your full table definition (ddl) I can only show a skeletal setup, but you should get the idea.

You are probably not exposing redis port to the sidekiq service try exposing this in docker compose. This probably may work.

After rebooting my computer, it now works...