Timeline for Keeping database connection [duplicate]
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 1, 2014 at 13:12 | history | closed |
gnat CommunityBot jwenting Bart van Ingen Schenau |
Duplicate of Creating database connections - Do it once or for each query? | |
| Aug 31, 2014 at 12:46 | review | Close votes | |||
| Sep 1, 2014 at 13:12 | |||||
| Mar 3, 2014 at 17:08 | comment | added | Evgeni | Keep in mind that having a single connection will prevent you from running queries in multiple threads. Also - opening a new connection when you need to make a db call is a safer/easier pattern, imo; measure a performance hit of opening/closing connections and make a decision whether it actually impacts perceived performance. | |
| Mar 3, 2014 at 7:41 | history | tweeted | twitter.com/#!/StackProgrammer/status/440391493237633024 | ||
| Mar 3, 2014 at 4:34 | vote | accept | c-o-d | ||
| Mar 3, 2014 at 4:31 | vote | accept | c-o-d | ||
| Mar 3, 2014 at 4:33 | |||||
| Mar 3, 2014 at 3:32 | answer | added | Adam Zuckerman | timeline score: 6 | |
| Mar 3, 2014 at 3:14 | comment | added | Adam Zuckerman | Yes, it can run out of connections. It is unlikely, but possible. | |
| Mar 3, 2014 at 0:42 | comment | added | c-o-d | @GilbertLeBlanc Can a connection pool run out of connections to give? | |
| Mar 3, 2014 at 0:28 | comment | added | Gilbert Le Blanc | You should open a connection when you need data, get the data, and then close the connection. You can use a connection pool to make managing the connections a bit easier. | |
| Mar 2, 2014 at 22:39 | history | asked | c-o-d | CC BY-SA 3.0 |