On 07/23/14 15:36, Dimitry Sibiryakov wrote: > Hi, All. > > Don't you think that IStatus interface is missing a method for forming > error > code-by-code? Definition of this method could be like this: > > IStatus::add(ISC_STATUS gds_code, ...); > > Usage would be like this: > > status->add(isc_sql_dialect_datatype_unsupport, Arg::IntParam, 1, > Arg::StrParam, 'TIME'); >
IStatus is missing very many things, but I still can't find a time to enhance it. 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. Next it should learn to store strings itself, and we will be able to drop crazy circullarAlloc from IMaster. ------------------------------------------------------------------------------ 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
