EnokMan
EnokMan
Perhaps your database is on an internal network. You can give me the results of your investigation. Like this, 
https://jira.mongodb.org/projects/RUST/issues/RUST-43?filter=allopenissues It seems that rust-mongdb already supports change streams, but there is no relevant documentation yet. If anyone is familiar with this, welcome to help
This project has completely used TS refactoring. Are you still interested in it? If so, you can try to implement this feature on this basis. Otherwise I will add it...
There is no precise plan, we will certainly consider you if you need it. If you can’t wait, you can implement it yourself and submit a PR. The current architecture...
not yet. At present, the driver will be completely rewritten using ts, and the Deno plugin will no longer be used. No functions will be added for the time being....
At the beginning, it takes a longer time to implement these same features
This question seems to be similar to #179 , does this help you?
This is indeed a problem with keepalive, which also exists in other database drivers of deno. I have recently used redis and pgsql in a production environment. Sending heartbeat requests...
Can you provide the smallest sample code that failed? So that I can locate the problem
I think it would be better for you to use another view to switch