On Dec 15, 2004, at 1:24 PM, Andy Kohler wrote:
> I'm not sure these 2 need to be separate options. Store the files in
> database, in whatever TEXT/CLOB/XML data-type is appropriate (and
> by your db)... assuming there are no performance reasons not to do so.
> That way everything's in one place, easy to get consistent backups.
> As far as data entry, if your maintenance front-end is web based (as I
> assume from "CGI forms"), what about using http upload (input
Again, thank you for the prompt reply.
Actually, the implementation you suggest was the path I was
considering. Unfortunately, this means leaving some sort of text lying
around on my file system for importing. Similarly, it poses the problem
of editing; in order to edit data in such an implementation I will need
to export the big chunk, edit, and re-import. That is sort of klunky,
but still it is what I was considering.