| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com>, Mircea Sarbu <msarbu(at)agora(dot)ro> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Using TEXT columns for binary content |
| Date: | 2003-04-21 16:18:57 |
| Message-ID: | 200304211218.57267.lamar.owen@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday 21 April 2003 12:01, Joe Conway wrote:
> Mircea Sarbu wrote:
> > There are some hidden drawbacks for this approach? (I don't need any
> > further processing on the binary content)
> There are people who have reported using this method successfully on the
> Postgres lists. Only downsides I can think of are:
> 1) You have to encode to base64 on the way in (bytea has to be escaped
> on INSERT/UPDATE too)
OpenACS uses this technique. The PostgreSQL driver for AOLserver (which
OpenACS uses) has code -- aolserver.sourceforge.net -- files, nspostgres.
GPL/APL dual-licensed, if that matters.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-04-21 16:21:10 | Re: stddev returns 0 when there is one row |
| Previous Message | Josh Berkus | 2003-04-21 16:14:43 | Re: [SQL] Yet Another (Simple) Case of Index not used |