| From: | Mike Mascari <mascarm(at)mascari(dot)com> |
|---|---|
| To: | Wolfgang Reichart <wolfgang_reichart(at)hotmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SPI and bytea columns |
| Date: | 2004-05-11 19:38:41 |
| Message-ID: | 40A12BC1.2090305@mascari.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Wolfgang Reichart wrote:
> hello!
> i want to insert jpeg pictures into a bytea field and i implemented a
> SPI extension. this function reads the jpeg-file from the filesystem,
> converts it into a octal-coded string to pass the sql-parser, and then
> exec's the insert statement. this is rather slow, and i'd like to insert
> using lower level postgres functions that handle binary data without
> base64- or escaped en-/decoding.
>
> did anyone something like this in the past?
Does it necessarily have to be stored in a bytea field? Why not
create your own type (CREATE TYPE) with utility functions to read
the image file from disk?
PostgreSQL really needs a maintained type library as a single
project where people can contribute types, functions, operators, and
aggregates, such as the recently discussed email type.
Mike Mascari
<joke>
Just be sure not to actually compress/decompress the JPEG or you
might get sued:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-11 20:22:15 | Re: Probably security hole in postgresql-7.4.1 |
| Previous Message | Andrew Hammond | 2004-05-11 19:19:55 | Re: Hacking MySQL Database |