Apparently MSSQL ODBC does an implicit DEALLOCATE for cursors, whereas Teradata doesn't. I'm testing a new close() method for the Teradata Adapter that does a self.connection.cursor.close() as well. So far so good. No reason why this couldn't be done in general (explicit close for each open) but I'll get it working for Teradata for now. Thanks
On Wednesday, October 16, 2013 5:43:09 PM UTC+11, Niphlod wrote: > on mssql I don't see anything like that, even raising to 15 pool_size and > flooding the poor rocket webserver.... there are at most 15 connections to > the backend. > > Il giorno mercoledì 16 ottobre 2013 00:30:37 UTC+2, Andrew W ha scritto: >> >> P.S. This may be an issue for all pyodbc databases MSSQL, DB2. >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
