On 19 Sep 2013, at 1:38 PM, Jonathan Lundell <[email protected]> wrote: > > What's the best way to catch a driver-specific OperationalError? I'm using > executesql to create a set of indexes (MySQL, as it happens), and I'd like to > catch, report & ignore existing-index errors. In an earlier version I was > getting InternalError, but now it's reported as > _mysql_exceptions.OperationalError. > > I can catch everything and use adapter.isOperationalError, I suppose (and > re-raise if no match). Is there a better way?
On reflection: a) we've switched default MySQL drivers, and b) I don't really care what the error is; I just want to report it back to the user. So just catching Exception should be fine. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
