Re: Loading Classes from Tables

Walden H. Leverich wrote:
> Yup, but in this case the class is the data. In my case I'm building a
> document generator. The generator asks the user a series of questions.
> These questions can be of a given type. The types are defined by
> classes. If we add a new type, I'd like to upload the class into the
> database and we're good to go. No programming changes required (other
> than creating the class that implements the question type). Hence, the
> classes that implement the question types are data, not code.

Sounds to me like you don't really want to store the CLASS in the
database ... but the OBJECT.  Storing the class actually does not
necessarily save the data ... just the code (at least the way I
understand it).

Using serialization you can extract the object's data into a blog and
store & retrieve it at any time.

Additionally, there are various mechanisms available to version the
serialized object so you can deal with object changes seamlessly.

david