From: | Jerry LeVan <jerry(dot)levan(at)eku(dot)edu> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Simplfied Bytea input/output? |
Date: | 2004-08-04 21:06:11 |
Message-ID: | 1D22AB50-E65A-11D8-BFBD-000393779D9C@eku.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the reply Kris...
I guess I did not state my case very clearly, what I would
like to see is a simple flexible tool that can get binary
data into the database...I can get it out fairly easy.
Of course it would be easy to "update" pg_hba.conf if you could
write files as postgres
Jerry
On Aug 4, 2004, at 3:40 PM, Kris Jurka wrote:
>
>
> On Wed, 4 Aug 2004, Jerry LeVan wrote:
>
>> INSERT INTO image (name, raster)
>> VALUES ('beautiful image', bytea_import('/etc/motd'));
>>
>> SELECT bytea_export(image.raster, '/tmp/motd') FROM image
>> WHERE name = 'beautiful image';
>>
>
> Doing this kind of file/read write is only useful if the client and
> server
> are on the same machine which is a kind of limiting restriction if you
> are
> trying to make a generic data browsing tool. Further any function that
> does file access like this must run with superuser permissions to
> prevent
> misuse which is another serious restriction.
>
> Kris Jurka
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2004-08-04 22:41:10 | Re: enforcing a join type |
Previous Message | Hicham G. Elmongui | 2004-08-04 20:53:58 | enforcing a join type |