Re: [PROPOSAL]a new data type 'bytea' for ECPG - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: [PROPOSAL]a new data type 'bytea' for ECPG
Date
Msg-id 7b727b360c78833d3e1e2e97d921aefe1ff0f5f3.camel@postgresql.org
Whole thread Raw
In response to RE: [PROPOSAL]a new data type 'bytea' for ECPG  ("Matsumura, Ryo" <matsumura.ryo@jp.fujitsu.com>)
Responses RE: [PROPOSAL]a new data type 'bytea' for ECPG
List pgsql-hackers
Matsumura-san,

> I try to explain as follows. I would like to receive your comment.
> ...

I'm afraid I don't really understand your explanation. Why is handling
a bytea so different from handling a varchar? I can see some
differences due to its binary nature, but I do not understand why it
needs so much special handling for stuff like its length? There is a
length field in the structure but instead of using it the data field is
used to store both, the length and the data. What am I missing?

Please keep in mind that I did not write the descriptor code, so I may
very well not see the obvious.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL



pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: libpq compression
Next
From: Alvaro Herrera
Date:
Subject: Re: use Getopt::Long for catalog scripts