On 08/12/14 19:43, Tom Coleman wrote: > On Aug 12, 2014, at 2:35 AM, Alex Peshkoff wrote: > >> On 08/11/14 23:57, Tom Coleman wrote: >>> On Aug 11, 2014, at 3:36 PM, Jim Starkey wrote: >>> >>>> You may be more interested in why something failed than just that it >>>> failed. >>>> >>>> An error mechanism should play nicely with the status vector to expose as >>>> much -- or as little as the user needs. Sometimes an error code is >>>> enough, sometimes a full formatted compound message is required. >>>> >>>> But a second call to pick up the "last" error would probably make almost >>>> every one happy. >>> Exactly. >>> >>> In fact I had this type of "Explain Last Error" call implemented >>> "somewhere", but I haven't been able to locate it. If and when I do I'll >>> know which database I used it on. >> May be GetLastError() in winapi? >> > > It was a method in a database interface that would retrieve status > information from the last failed database call. It might have been Firebird. > > And it Definitely would not have been Windows. :)
Hmm - may be some wrapper around ISC API. There are many wrappers. This method has one disadvantage - it requires TLS in MT environment, and when talking about TLS - on my mind it should be used only when nothing else can be done, better be never used at all. ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
