Skip site navigation (1) Skip section navigation (2)

Re: Bytea/Base64 encoders for libpq - interested?

From: "Joe Conway" <joseph(dot)conway(at)home(dot)com>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Karel Zak" <zakkr(at)zf(dot)jcu(dot)cz>, "Joerg Hessdoerfer" <Joerg(dot)Hessdoerfer(at)sea-gmbh(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bytea/Base64 encoders for libpq - interested?
Date: 2001-09-04 15:37:35
Message-ID: 00d301c13557$85b0d4f0$0705a8c0@jecw2k1 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> > On a related note, are there any other bytea functions we should have in
the
> > backend before freezing for 7.2?
>
> The SQL standards has a lot of functions for BLOB...
>

OK - thanks. I'll take a look.

> > I was thinking it would be nice to have a
> > way to cast bytea into text and vice-versa, so that the normal text
> > functions could be used for things like LIKE and concatenation.
>
> Better write a native LIKE function for bytea, now that some parts are
> threatening to make the text-LIKE function use the locale collating
> sequence.  (Multibyte aware text could also have interesting effects.)
>

Sounds like good advice. I'll try to get both the cast functions and a
native bytea LIKE function done.

-- Joe


In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-09-04 15:37:48
Subject: Re: [PATCHES] to_char and Roman Numeral (RN) bug
Previous:From: Bruce MomjianDate: 2001-09-04 15:33:30
Subject: Re: [HACKERS] getting the oid for a new tuple in a BEFORE

pgsql-patches by date

Next:From: Bruce MomjianDate: 2001-09-04 15:37:48
Subject: Re: [PATCHES] to_char and Roman Numeral (RN) bug
Previous:From: Bruce MomjianDate: 2001-09-04 15:35:16
Subject: Re: Read transactions don't work on 7.0.x db's Disregard my other

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group