have shared data for different client with same connection parameters
See original GitHub issueIf creating 2 Redis clients with same connection parameters, I would like to have shared data between them
const Redis = require('ioredis-mock');
const client1 = new Redis('localhost', 6378);
const client2 = new Redis('localhost', 6378);
await client1.hset('testing', 'test', '2');
const val = await client2.hget('testing', 'test');
console.log(val) // should output 2
As I see it, it can be implemented by mapping connection string to a DB object
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
SQL Server Reporting Services (SSRS) Shared Dataset
In the SQL Server Reporting Service (SSRS) report development process; we can use a beneficial feature which is called the “shared dataset”.
Read more >Ways to share an Access desktop database - Microsoft Support
Some limitations include reliability and availability if there are multiple simultaneous users changing data since all database objects are shared.
Read more >Should I share types between a Web API service and its client ...
In both options, you are effectively sharing types between the client and the server.
Read more >How to share a SINGLE report with ALL your clients
First, let's talk about the available ways of sharing. To deliver a solution to your client, you have two options:.
Read more >15: 20.11. Client Connection Defaults - PostgreSQL
The default value for this parameter is "$user", public . This setting supports shared use of a database (where no users have private...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
how about a feature like this:
good issue
I will request PR