Re: Error conditions
"Geir Ove Grønmo" <[email protected]> Thu, 15 Mar 2007 13:32:11 +0100
| Newsgroups | gmane.text.xml.xtm.tmql |
|---|---|
| Message-ID | <[email protected]> |
On 3/15/07, Lars Marius Garshol <[email protected]> wrote: > > * Geir Ove Gr=F8nmo > > > > In the hope that it might be useful for the discussion, the new JDBC > > 4.0 specification has rearranged the java.sql.SQLException class into > > two different types of exceptions: > > > > - transient exceptions > > > > - non-transient exceptions > > This is a categorization that adds value, I agree. The trouble (from > our point of view) is that query errors are all non-transient. TMQL > doesn't deal with transient errors at all. Note that tolog *does* can trigger transient errors. Here's an query that *can* trigger such an error: $ONTOPIA =3D i"http://www.ontopia.net/"? *Iff* there is no topic with the given subject identifier in the topic map then a transient error will be triggered. If suddenly someone adds the topic to the topic map the query will suddenly work. > Those are an API/ implementation issue. Yes, but as you see above there *can* be transient errors that are triggered based on the contents of the topic map. I do not know TMQL well enough at this time to say whether this is the case for TMQL. > > E.g. syntax errors are considered non-transient errors. > > Exactly. And type errors, and incorrect parameters, and ... > > Transient errors are things like network failure, out of memory, lock > timeout, etc. Yes. --=20 Geir O.