Hello Dmitry,

>>> XSQLDA alone was never able to satisfy the API level developers (maybe
>>> except the very early days). In order to get more detailed information,
>>> there are special tags for isc_dsql_sql_info(). For example, it can
>>> deliver you all the information necessary to manually fill the XSQLDA
>>> (this is basically what fbclient does behind the scene). So, unless
>>> we're speaking about a whole new API, I don't think that such changes to
>>> XSQLDA are a good idea. Just ask us about adding a new statement
>>> information tag and use the proper API call instead.
>>
>> Consider it asked. :-)
>
> Indeed, it's simple:
>
> Can "sqlscale" be filled with N where N is the number of characters in
> the result.

Can it?

> If this is possible, does it require a new server or both a server and
> a client?
>
>> Also, please make the XSQLDA and XSQLVAR documentation very clear about
>> the problems of parsing/trimming/interpreting the data buffer for
>> char(n) columns for variable-length charsets. I expect there are a lot
>> of bugs out there already...

With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!

Database questions? Check the forum:
http://www.databasedevelopmentforum.com