Tim Uckun wrote:
> I understand what you are doing I think. It's a neat solution. But how
> do I store that stuff in a database?

@opts contains the keys and the boolean values (if you go for the 
extended version, you may have to go through the values and turn the 
symbols and procs into booleans.) I'm not sure what kind of database 
structure you have, but those could be used as name-value pairs of some 
sort. That's how I'd do it.


Cheers,
Daniel