On 03/21/14 19:39, Dimitry Sibiryakov wrote:
> 21.03.2014 16:35, Mark Rotteveel wrote:
>> With field length I mean the declared length (for single byte character
>> sets) or 4*declared length for UTF8), eg VARCHAR(500): declared length is
>> 500, not 502.
> This is data limit in chars and in mo
21.03.2014 16:35, Mark Rotteveel wrote:
> With field length I mean the declared length (for single byte character
> sets) or 4*declared length for UTF8), eg VARCHAR(500): declared length is
> 500, not 502.
This is data limit in chars and in most of other APIs it is returned
separately from
le
On Fri, 21 Mar 2014 16:23:38 +0100, Dimitry Sibiryakov
wrote:
> 21.03.2014 14:29, Mark Rotteveel wrote:
>> AFAIK the length is the maximum length (in bytes) of the field, not of
>> the
>> buffer.
>
>What do you call "field length"? In ODS (AFAIK) VARCHAR is kept with
>these two extra
> by
21.03.2014 14:29, Mark Rotteveel wrote:
> AFAIK the length is the maximum length (in bytes) of the field, not of the
> buffer.
What do you call "field length"? In ODS (AFAIK) VARCHAR is kept with these
two extra
bytes as well, so maximum length of filed on disk and in memory is two bytes
big
On Fri, 21 Mar 2014 14:18:07 +0100, Dimitry Sibiryakov
wrote:
> Hello, All.
>
>In new API data length returned for SQL_VARYING still two bytes
smaller
>than real
> buffer requirement. Does it have a justification other than "make
> everything the same way
> as it was in old API"?
AFAIK
