Bruce Momjian <[EMAIL PROTECTED]> writes: > Where did we leave this? I don't think adding a datatype just to provide base64 encoding is a wise approach. The overhead of a new datatype (in the sense of providing operators/functions for it) will be much more than the benefit. I think providing encode/decode functions is sufficient... and we have those already, don't we? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
- [HACKERS] Bytea/Base64 encoders for libpq - interested? Joerg Hessdoerfer
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Karel Zak
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Bruce Momjian
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Tom Lane
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Bruce Momjian
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Joe Conway
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Bruce Momjian
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Tom Lane
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Joe Conway
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Peter Eisentraut
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Tom Lane
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Joe Conway
- Re: [HACKERS] Bytea/Base64 encoders for libpq - int... Joe Conway