On 06/14/12 18:38, Vlad Khorsun wrote: >> Is it enough to agree that keeping warnings in our API is the only >> correct solution? > I, personally, prefer to have warnings, but, probably it should be > delivered not using status-vector. If we can produce and deliver many > warnings per statement (or per API call) it will be the best, as for me. >
>From SQL2008: If a condition is raised that causes a statement to have no effect other than that associated with raising the condition (that is, not a completion condition), then the condition is said to be an exception condition or exception. If a condition is raised that permits a statement to have an effect other than that associated with raising the condition (corresponding to an SQLSTATE class value of successful completion, warning, or no data), then the condition is said to be a completion condition. Here I want to pay an attention - we already return no_data completion condition not in status vector. Therefore on my mind nothing prevents us from returning warnings also not in it. May be we should add some more functions to IStatus to check not for exceptions, but also for warning and no_data? To separate warnings from exceptions and to have single interface to check statement conditions? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
