On 11/08/2014 16: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. > > Always remember that internally, the old API is an user of the new API.
If it can do easily, so you can do the same you were doing if you start to use the new API. Adriano ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
