What is the reason to use the encode/decode rules shown in table 3-7 (PG docs) for the "bytea" datatype. I think the "hex string" SQL99 use, looks much more convinient. Is there any particular reason not to follow SQL99 in this case??? Advantages of the hex string: - the leng of the buffer is known. - easier, (faster?) conversion - no extreme cases (all of the bytes are 0 -> '\\000')
For a new new own defined type, is it possible to define the maximum length of the object just like TEXT(N), CHAR(N) do it?
