Subject | Re: [firebird-support] Re: What are the trade-offs of CHAR vs. VARCHAR? |
---|---|
Author | Mark Rotteveel |
Post date | 2019-11-14T19:29:39Z |
On 14-11-2019 19:02, Dimitry Sibiryakov sd@...
[firebird-support] wrote:
Reference:
https://www.firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/html/fblangref25-datatypes.html#fblangref25-dtyp-tbl-dtypinfo
And that part of the documentation is unfortunately wrong (although I'm
not sure why the language reference even cares to describe such an
implementation detail).
That table contains some more problems, for example for VARCHAR it says
the length is in "two trailing bytes".
Mark
--
Mark Rotteveel
[firebird-support] wrote:
> 14.11.2019 18:01, blackfalconsoftware@... [firebird-support] wrote:Actually Dimitry, Steve was quoting from the Firebird 2.5 Language
>> However, the PDF language manual I have for version 2.5 does in fact state the following...
>>
>>
>> "A fixed-length character data type. When its data is displayed, trailing spaces are added
>> to the string up to the specified length. Trailing spaces are not stored in the database
>> but are restored to match the defined
>> length when the column is displayed on the client side. Network traffic is reduced by not
>> sending spaces over the LAN. If the number of characters is not specified, 1 is used by
>> default."
>
> No, it something completely different from what is written in Language Reference and it
> is plain wrong.
Reference:
https://www.firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/html/fblangref25-datatypes.html#fblangref25-dtyp-tbl-dtypinfo
And that part of the documentation is unfortunately wrong (although I'm
not sure why the language reference even cares to describe such an
implementation detail).
That table contains some more problems, for example for VARCHAR it says
the length is in "two trailing bytes".
Mark
--
Mark Rotteveel