Question re: WARNING: Creating a duplicate database object for the same connection

[CalebEverett]

Is the right way to set this up in an Express app to create a separate db module per the example and then require that in each set of routes? I've done that, but am still getting the warnings. Do I need a separate database object for each set of routes or can you recommend otherwise? Thanks,

[vitaly-t]

• I removed that example before you even posted this
• That example works in your code, which I tested here, couldn't commit the change though, as you didn't give me the rights.

[MatthewJamesBoyle]

@vitaly-t hmm strange I could see that code until a few minutes ago on this discussion thread. Hence me quoting your reply above, as it was still visible. Glad its cleared up now though!

I added you as a contributor to the project, thanks! I can tidy up the readme of it and can perhaps serve as an example for others using your great library with next.js

[vitaly-t]

I won't have time for this today, you'll be better off just following the pattern as explained.

[vitaly-t]

@MatthewJamesBoyle Did you get this working in the end?

[MatthewJamesBoyle]

@vitaly-t no, I still get a development warning no matter what I try. I have moved to solve this problem with infrastructure instead for now.

[vitaly-t]

Well, you probably did something wrong again then, because when I just followed that code example I provided, for your demo app, it just worked, there was no warning anymore. It works.

[MatthewJamesBoyle]

Do you want to push it so I can see rather than just telling me I'm doing something wrong?

[vitaly-t]

I didn't have time to re-do it, so here's zipped code.

[markojanicic-sas]

Hello, reopening this. @MatthewJamesBoyle did you solve this? Currently having the exact same issue. Would love to see your JS take on above solution.

[jcollum-nutrien]

Here it is 5 months later and I'm seeing this issue in 11.5.4. Investigating, maybe we are doing something wrong in our code.