Well, assuming you can store a reasonable large text file in any database,
you can also look at uuencoding / base-64 encoding as a way of storing
things in the database.
It's more easily ported than either bytea or large objects.
On Wed, 10 Sep 2003, Network Administrator wrote:
> I'd actually like to get some comments on this too because for compatibility and
> throughput issues, I would think that storing the file path in the database
> instead of the actually file would be "better". I've done one application like
> this in the past that very worked well. I'm getting ready to do the final
> e-commerce integration on a new site and if there is an advantage to storing the
> files in the database (in this case about 300 jpeg images for a t-shirt site)
> I'll try that out. I'll have to research that base64 encoding part because I'll
> only every do text dumps.
>
> Keith-
>
> Quoting Jeff Eckermann <jeff_eckermann@yahoo.com>:
>
> > --- Jonathan Bartlett <johnnyb@eskimo.com> wrote:
> > > I'm a big fan of bytea. In every case where I've
> > > done the filesystem
> > > method I wished I hadn't.
> >
> > For the education of me and maybe others too, why was
> > that? i.e. what problems did you run into, that bytea avoids?
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! SiteBuilder - Free, easy-to-use web site design software
> > http://sitebuilder.yahoo.com
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 8: explain analyze is your friend
> >
>
>
