I used base64 and even hex , and respectively if you've got 8G of image data
it's going to bloat by 1.5 to 2 times. Uploading files to a server-side image directory
makes the backup process split into dumping the postgres database and targzipping a directory tree,
but quite a few previous applications in richard's domain have gone down that path , if I remember
genie and md3.
On Tue 24/11/09 11:36 , "richard terry" rterry(at)pacific(dot)net(dot)au sent:
> On Tuesday 24 November 2009 22:23:01 Jasen Betts wrote:
> > > If you really want to have your blobs
> stored in the database, I'd> > recommend using a "bytea" column
> as Jean-Yves suggests -- this way you> > won't need superuser privs to insert your
> data, and you'll avoid the> > additional complication of lo_import() only
> working on files on the> > server's filesystem. There might be a way
> to insert OID records> > without using lo_import() and without
> needing PG superuser privileges,> > but I haven't tried.
> >
> > there is an sql method but I have not found the
> documentation (it's used in> SQL backups) there's also the libpq lo_open
> lo_read lo_write functions>
> > that said bytea works well for most purposes, if
> working in raw sql> encode() can be used to convert the
> double-escaped data to more easily> handled base64
> >
> I've settled for bytea at the moment and using the ordinary gambas database
> object its workingly simply and quickly, at least with images so far.
>
> thanks for all the replies.
>
> Regards
>
> Richard
>
> --
> Sent via pgsql-novice mailing list (p
> gsql-novice(at)postgresql(dot)org)To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>
>