On 07/24/14 12:43, Dimitry Sibiryakov wrote: > 23.07.2014 14:17, Alex Peshkoff wrote: >> First of all - errors, warnings, information codes (we do not have one >> now, but they are present in SQL spec) and successful completion codes >> (like EOF in fetch) should be separated. > EOF in fetch is separated. It doesn't go into status at all. > But I have no idea what to do with warnings and information codes in > application. > Handling of errors is obvious: an exception must be thrown, but what routine > that execute > queries should do when it detected an information code?.. >
Reviewing standard I've understood that I was not exactly right here. There are: - exception condition (error), - warnings, - no data (EOF) condition, - success EOF is really separated. I.e. the only thing remaining for us is to decide how to handle warnings better. Mixing them with errors (in the end of vector) is far from ideal solution. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
