To separate package customizations from release versions, I like to place the custom code in the ${serverroot}/www directory tree.

For example, if the photo-album package is mounted at /fotos3 and /fotos4, I can modify some aspects of /fotos4 by:

Copying files from ${serverroot}/packages/photo-album/www to ${serverroot}/www/fotos4/

and modifying them. However, xql files in the www directory appear to get loaded only the first time referenced. Changes to them require a server restart.

Since there is some development activity inspired from ROR etc. to make xql files work in the same manner as .adp/.tcl file pairs, can we expect the xql files to behave more like .adp/.tcl files (ie. not requiring a server restart) sometime soon?

Thanks, Jade. I plan to learn arch at some point soon. However, I do not see a revision control system affecting an openacs instance to reload xql files in the www directory tree (like "watch files" does from the package manager /acs-admin/apm/).

I'm posting a suggestion to bugtrackers' acs-admin package, though maybe there is a better place for it.

For the most part all your XQL files should be contained in a package and mounted in the site-map.

I could be wrong, but aren't xql files the only sql situation where you can use literal variables, ie, a variable where clause?

select event_id

from   events

$where_clause

I had no success getting this to work in db_* functions in my tcl files.

Thanks, Jose!