Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add the "current_database()" to our builtins
See original GitHub issuePostgres has a nice current_database() function that returns the name of the database you’re connected to. This is a nice utility function to have. The proposal is to map it onto sys::get_current_database().
The main reason I ran into this was that I was working on a fix to handle “cannot drop the currently open database” error and realized that the easiest way to write a test for this would be to actually ask the name of the test database first and then attempt to delete it, rather then set up a whole different test where I control the test database name.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 for the separate functions
Closing this, since the subject is done, and
current_userdepends on a functional role system, which we don’t have yet.