I want to store templates in the database, and I'm just looking for tips or ideas from others that may also be doing this.
I'm using Catalyst to serve dynamic content. Catalyst has a default "action" (controller/handler) that is called when no other action can be found for the request. I'm currently using this default action to serve static content; the default action simply stats the uri->path relative to some directory and if found the content is fetched and passed to process(). The point of placing the static content in the database is to use the same application to manage the static content that is used to manage the dynamic part of the application. My main concern is the loss of the hierarchy the file system provides -- for example, being able to easily move an entire tree of files. My plan is to just have a unique column "path" and match on that. Anyone doing this and *not* just matching on a path? That is, defining the hierarchy in the database? As a programmer, it's hard not to expect everything to be under revision control. So, I'm wondering what others might be doing to provide revision control to templates stored in the database. -- Bill Moseley [EMAIL PROTECTED] _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
