Wt

The Dbo backend for Postgres currently depends on a bad_lexical_cast exception to parse boolean values. It seems to work fine, though it can generate a lot of exceptions in normal processing. In looking at another issue, I implemented a trivial patch to eliminate the exceptions by checking for the boolean case first. Unlike the current code, it won't handle upper-case "T" or "F", but I'm not sure how those would get returned by Postgres. In any case, I've attached the patch for your review. It has only been lightly tested.