Timeline for pyodbc.connect timeout argument is ignored for calls to SQL Server
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 14, 2020 at 16:56 | comment | added | Asraful | @Bryan timeout is in connection object level , means after connection object populated , is it possible to pass any timeout while trying to connect , i mean login timeout , as postgres we can pass such timeout as : psycopg2.connect(user = data['username'], password = data['password'], host = postgres_host, port = postgres_port, database = postgres_db, connect_timeout=connect_timeout) | |
| Oct 18, 2012 at 23:24 | comment | added | Bryan |
@ChrisGuest Understood. The timeout variable is new information to me also, and it wasn't immediately apparent to me what needed to be done to take advantage of it. Hopefully this will help those who run across it and are dense like me :-)
|
|
| Oct 18, 2012 at 23:23 | history | edited | Bryan | CC BY-SA 3.0 |
added link
|
| Oct 18, 2012 at 22:35 | comment | added | ChrisGuest | While I've accepted cravori's answer by precendence, you give the same solution with a more detailed explanation. Thanks for that. | |
| Oct 18, 2012 at 12:30 | history | answered | Bryan | CC BY-SA 3.0 |