| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | "Matsumura, Ryo" <matsumura(dot)ryo(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL]a new data type 'bytea' for ECPG |
| Date: | 2018-10-26 18:43:18 |
| Message-ID: | e17036827f7a42f1c7bbf501f644e2b2ea20eced.camel@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2018-10-26 20:38:02 | Re: Buildfarm failures for hash indexes: buffer leaks |
| Previous Message | Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= | 2018-10-26 16:11:59 | Re: [PATCH] Tab complete EXECUTE FUNCTION for CREATE (EVENT) TRIGGER |