From: | Zeugswetter Andreas <andreas(dot)zeugswetter(at)telecom(dot)at> |
---|---|
To: | "'Bruce Momjian'" <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "'pgsql-hackers(at)hub(dot)org'" <pgsql-hackers(at)hub(dot)org> |
Subject: | AW: AW: [HACKERS] attlen weirdness? |
Date: | 1998-03-12 08:56:36 |
Message-ID: | 01BD4D9D.31C15540@pc9358.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Right now: yes, but I would like to see the char() type changed to a fixed length type (which it really is)
> then it would have the length in attlen. Right now the length for char and varchar is in atttypmod.
>
Again, we can do this, but we then have to have atttypmod available in
all places where we check for length. I will add it to the TODO list.
I am starting to see the problem, only atttypmod is passed around not attlen.
Therefore even if we do this, the char() length of a column still has to be in atttypmod.
So it will stay the same for Julie, whether it is taken out or not. But since it is really
hard for a generic application like ODBC, maybe we could change atttypmod to not
include the VARHDRSZ, most of the time it is needed without VARHDRSZ anyway ?
I am starting to think that this would be more important than to remove the 4 bytes.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | PostgreSQL | 1998-03-12 09:10:43 | Failing to get email from list or to susbscribe |
Previous Message | Vadim B. Mikheev | 1998-03-12 07:06:04 | Re: [HACKERS] Timetravel vs checkpointing and no read-locking |