|
|
Posted by Tim Streater on 03/27/07 17:39
In article <_3bOh.30760$GI.9369@newsfe2-gui.ntli.net>,
Mary Pegg <invalid@invalid.com> wrote:
> Tim Streater wrote:
>
> > In article <fqaOh.26793$267.1379@newsfe6-gui.ntli.net>,
> > Mary Pegg <invalid@invalid.com> wrote:
> >
> >> Why? Why would I *want* to put non-relational data in a relational
> >> database? Why would I *want* to use a database as a filesystem?
> >>
> >> Just saying "it works fine" is not enough.
> >
> > Depends on your needs, dunnit?
> >
> > If I'm providing as it might be a web page for our engineers to see what
> > the access procedure is for some site, that info is in the database. But
> > the hosting organisation might provide an extra Site Procedures doc,
> > that I also put in the database so the engineer can download it as
> > needed, at the same web page.
> >
> > I'm not going to put it in some entirely separate filesystem that they
> > might not have access to while offsite, now am I.
>
> It'll look the same to the user whether the document is stored as a
> BLOB in the database or as a file.
But they won't have to go arsing about looking for it. I'll have a
button on the page that'll download it for them. NB, I got *asked* for
this feature by folks here.
-- tim
Navigation:
[Reply to this message]
|