Sure it can fail. You can pass bad SQL, for example, or try to read
something your DB user account doesn't have permission to read.
That said, I don't see why you'd use try/except. Instead, use
try/finally to commit the transaction whether or not the SELECT fails.
There is no need to "roll back" a SELECT, since it doesn't modify data.*
* Selectable stored procs can modify data, but I don't think that's
what you're asking about.
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
Borland newsgroup denizen Sergio González has a new CD of
Irish music out, and it's good: http://tinyurl.com/7hgfr