Disclaimer: this issue is minor and will certainly be a post-1.0 ticket if one is opened.
When a database connection goes stale (e.g. from going unused for a long period of time), the MySQL backend automatically re-opens the connection on the call to connection.cursor() in db/backends/mysql/base.py However, the Oracle backend doesn't do this. There isn't a clean way to do this in Oracle, because the MySQLdb module's connection objects have a ping() method that can check whether the database connection is live, whereas the cx_Oracle connection objects have no such method. However, we could still try to open a new cursor, catch any cx_Oracle exceptions, and if they occur, re-open the connection and then open and return a cursor from the new connection. Would this be a desirable behavior? If so, I can open a ticket and submit a patch (though I'll probably wait until after 1.0 comes out to work on the patch, just to make things easier). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
