another option is using sqlite for storing images. All data is in single file. (or files if you organize it that way) easier backup etc... you have some db benefits and retaining solid speed vs file system. Haven't used this, but seems as viable option to explore.
Esmin
On Fri, Jun 3, 2011 at 6:33 PM, Carl von Clausewitz
<clausewitz45@gmail.com> wrote:
Thanks for the replies, and suggestion from Ognjen, Ben Chobot, John R Pierce, Tomás, and Karsten... I checked the links, and I decided, that I cannot decide :-) because I don't know, how large could be the infrastructure for this. If I store the images, and scanned docus in the database, a radically larger enviroment will be needed, than if I store only the link. My boss will decide, and I will implement anything, that he wants, I just wanted to collect some experience, that you have, and that you have provided form me, and many thanks for it :-)
Thanks again,
Regards,
Carl.
2011/6/3 Karsten Hilbert
<Karsten.Hilbert@gmx.net>On Fri, Jun 03, 2011 at 07:15:40AM +0200,
tomas@tuxteam.de wrote:
> but you wouldn't have large blobs of data clobbering your "regular" queries.
select * from my_table_with_bytea_column;
anyway.
> You could pass the scans and pics piecemeal between client and database
At least for retrieval even BYTEA can be accessed piecemeal:
select substring(bytea_column from <start> for <number_of_bytes>)
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346