Thanks for the suggestions.

The direction i was going with the check was so that there could be different methods in the table that handle the different types of call (or all of them).

The eventual aim of this code is to have a client tool which talks directly to the database to modify the code, in a similar manner to vignette story server (but with perl instead of TCL).

At the moment the working code lets you store objects in the database, (that at the moment can be html, data (using Data::Dumper) and straight perl code. You can then write various subs that act upon the different types of object, such as the edit sub, which lets you edit (by means of a form at the moment) the object. The sub then passes the result of the form back to itself.

At the moment this is fairly slow, but I think that after it's implemented with mod_perl, I can use caching (and possible storage of byte-code) to reduce the database calls and the number of eval's needed in a typical.

The eventual aim of this is to allow the rapid development of dynamic sites.

Thanks for your comments.

Stephen