Re: encode in base code - Mailing list pgsql-patches

From Marko Kreen
Subject Re: encode in base code
Date
Msg-id 20010703085529.A1956@l-t.ee
Whole thread Raw
In response to Re: encode in base code  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: encode in base code  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
On Mon, Jul 02, 2001 at 07:50:45PM +0200, Peter Eisentraut wrote:
> Marko Kreen writes:
> > Put encode() into base system.  Used part of Alex' patch
> > for docs, hope he does not mind ;)
>
> Please use #include "", not #include <>, for PostgreSQL's header files.
>
> Would you mind changing the copyright to match the rest of the source?
>
> Put everything in encode.c (not varlena.c), and put encode.c in utils/adt.
>
> I think we've covered before that 'uint' is not a standard data type.
> VARSIZE is of type int32 (signed).
>
> To convert from text to C string, use textout().
>
> Also, I think the term "encode" is already overloaded for multibyte use.
> Maybe it needs to be qualified, such as "binary_encode".

Used 'unsigned' in encoding code.

--
marko


Attachment

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: DROP CONSTRAINT (UNIQUE) preliminary support
Next
From: Anders Bengtsson
Date:
Subject: Re: [PATCH] Cleanup of JDBC character encoding