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.
DatabaseFacade.CanConnect doesn't actually check anything
See original GitHub issueDatabaseFacade.CanConnect is supposed to determine whether the database is alive and can be connected to. The default implementation in RelationalDatabaseCreator calls Exists, whose implementation in SqlServer (and Sqlite and Npgsql) is to simply open and close a connection. As far as I’m aware, assuming connection pooling is enabled this doesn’t actually do any sort of communication to the database. We should consider implementing CanConnect by doing a raw SELECT 1 roundtrip, or possibly opening and closing a non-pooled connection.
Note that ASP.NET’s EF health probe is built over this API.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (7 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
I’m gonna try repro the other issue again on 2.2 in the coming week, I’ll keep you posted
I don’t have any significant pushback against
SELECT 1.