I am not sure I understand. If the exception is raised by the database (postgresql), the driver catches it and re-raises it usually as a OperationalError. You need to look into psycopg2 documentation. Web2py does not capture the exception raised by the driver (except in the case of failure to insert for KeyedTables)
On Jan 14, 11:34 am, haftish21 <haftis...@gmail.com> wrote: > In one of my controller actions required to get the exact EXCEPTION > raised by postgreSQL function. How could I fetch the RAISE EXCEPTION > error using psycopg (or the connection cursor)?
-- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.