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
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
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-
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::S
