Subject | Re: [ib-support] ato increment / IDENTITY |
---|---|
Author | Frank Ingermann |
Post date | 2001-06-15T17:00:31Z |
Hi Ann,
"Ann W. Harrison" wrote:
(probably an faq, feel free to slap me if it is <g>)
you say all the data in a record is stored with run-length compression, thus
32 or 64bits doesn't make much of a difference when the uppermost bits are all
zero. Ok. But what about the network traffic? The question is:
- is the data stream from a query result sent across the wire in compressed
form, and then decompressed by the gds32.dll on the client side, or is it
decompressed by the server and then sent in "full length" to the client?
This would make a great difference for the choice of data types
(Smallint vs. Numeric(18,0) included), but esp. between Char or VarChar.
so how many bytes would go across the wire for: (assuming 1 byte per char)
a) a CHAR(100) with 10 Chars (<> blank)
b) a CHAR(100) with 100 Chars
c) a VARCHAR(100) with 10 Chars
d) a VARCHAR(100) with 100 Chars
(and please don't tell me it's 100 bytes in either case ;-)
tia & regards,
fingerman
"Ann W. Harrison" wrote:
>after following this thread, i'm just curious about one more thing:
> At 10:30 PM 6/13/2001 +0100, Ray Drew wrote:
> >Bottom line... Would you recommend using Int64 for all generated pk values?
>
> yes.
(probably an faq, feel free to slap me if it is <g>)
you say all the data in a record is stored with run-length compression, thus
32 or 64bits doesn't make much of a difference when the uppermost bits are all
zero. Ok. But what about the network traffic? The question is:
- is the data stream from a query result sent across the wire in compressed
form, and then decompressed by the gds32.dll on the client side, or is it
decompressed by the server and then sent in "full length" to the client?
This would make a great difference for the choice of data types
(Smallint vs. Numeric(18,0) included), but esp. between Char or VarChar.
so how many bytes would go across the wire for: (assuming 1 byte per char)
a) a CHAR(100) with 10 Chars (<> blank)
b) a CHAR(100) with 100 Chars
c) a VARCHAR(100) with 10 Chars
d) a VARCHAR(100) with 100 Chars
(and please don't tell me it's 100 bytes in either case ;-)
tia & regards,
fingerman