Are you really sure you want to do this? It's usually a bad idea. Putting files (templates, images, etc.) in your database makes them hard
to edit and breaks all of the good tools (grep, locate, emacs, cvs,
etc.) that exist for file manipulation.
Which makes me wonder... (segfault in thought process, dumping to STDOUT)
Would it be so hard to write a simple FUSE based database-filesystem for this very (and similar) purposes?
/mnt/contentdatabase/tablename/fileid
Mount the filesystem with bindings for each table...
[tablename] filename=column (must have a unique constraint) filecontent=column (must be large text/blob/clob/etc)
Why would give "normal" file access while holding it in the database
Adam K
_______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
