title: Avoid database calls using incorrect database connection
body: <p>I'm working on some large software that has a current database connection open that connects to one database, but unfortunately it doesn't use the link identifier in it's query calls.</p>
  
  <p>Now I had to open a connection to another database; this works fine, however all calls to database functions now seem to use the second connection I opened (they use different arguments).</p>
  
  <p>Is there any way to avoid this and get the queries to go back to using the first connection opened or will I have to add a <code>link identifier</code> to all the other calls as well?</p>
  
  <p>Can I just close the second connection and then it will go back to using it or not?</p>
  
  <p>I know I can avoid opening a second connection by using listing the db in the query as well, but I don't really want both databases to use the same credentials.</p>