From 9b775726629fe804af71a72c914933025ee21f75 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 4 Sep 2001 03:17:54 +0000 Subject: [PATCH] Add mention of bytea data type and escaping rules. --- doc/src/sgml/datatype.sgml | 27 +++++++++++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index ce9fffa0c2..7efc0a7589 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1,5 +1,5 @@ @@ -83,6 +83,12 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.60 2001/08/31 01:55:25 is rectangular box in 2D plane + + bytea + + binary data + + character(n) char(n) @@ -782,7 +788,11 @@ CREATE TABLE tablename (text Variable unlimited length - + + bytea + binary data + + @@ -829,6 +839,19 @@ CREATE TABLE tablename ( + + The bytea data type allows storage of binary data, + specifically allowing storage of NULLs which are entered as + '\\000'. The first backslash is interpreted by the + single quotes, and the second is recognized by bytea and + preceeds a three digit octal value. For a similar reason, a + backslash must be entered into a field as '\\\\' or + '\\134'. You may also have to escape line feeds and + carriage return if your interface automatically translates these. It + can store values of any length. Bytea is a non-standard + data type. + + The storage requirement for data of these types is 4 bytes plus the actual string, and in case of character plus the