in theory the connections to the original database should become invalidated when the cursor() function on the connection throws an error. an invalidated connection will then try to connect again on the next reuse which will call your function.
however in practice ive noticed thats cursor() is not where most DBAPIs throw the error, they throw it upon the execute() call. if this is the case with firebird, then for firebird to automatically detect dropped connections the do_execute() method in the FB dialect would need to be implemented, which catches the specific exception raised corresponding to a non-connecting database and invalidates the connection. see the mysql.py module for an example. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
