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 e17036827f7a42f1c7bbf501f644e2b2ea20eced.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  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
RE: [PROPOSAL]a new data type 'bytea' for ECPG  ("Matsumura, Ryo" <matsumura.ryo@jp.fujitsu.com>)
List pgsql-hackers
Hi Ryo-san,

> # Please call me Ryo. Matsumura is too long.

Thanks.

> In Pro*C, the data should be represented as hex format C string.

Just to clarify, there is no special datatype for binary data?

> bytea as a type of table definition may correspond to BLOB in the
> standard.

Would we prefer to add a blob datatype then?

> It seems that there is no defact and no product following to the
> standards.
> I wonder whether bytea should follow to the standard completely or
> follow to existing varchar for usability.

Do you see any disadvantage of following the standard? I don't really
see where the usability drawback is. In general I would prefer being as
close to the standard as reasonably possible.

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: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
Date:
Subject: Re: [PATCH] Tab complete EXECUTE FUNCTION for CREATE (EVENT) TRIGGER
Next
From: Jeff Janes
Date:
Subject: Re: Buildfarm failures for hash indexes: buffer leaks