After thinking about this some more, I would like to clarify.  When I
don't catch the exception, TG does not throw it.  Instead, it appears
to keep on going and throw the next exception it runs into.   My code
inherits from fastdata.DataController.  An exception should be thrown
in the create method because of the unique constraint in the database.
Instead, TG is throwing an exception sometime later when it tries to
use the connection for a select.  The connection is no good because the
first exception (which TG hid) invalidated the transaction.  What
bothers me is that TG is not throwing the exception when it should.

Randall

Reply via email to