I'd like to use a database for storage if possible because some users may want to be able to access the data using their own tools.
I think I have a workable solution to this. I'm creating an 'Attributes' class with a many-to-one relationship to the main objects table, an attribute name column and an attribute value column. All the 'duck-typed' attributes will go in here. It's a fairly limited solution with some obvious drawbacks, such as only supporting attributes of a single type per class, but should be sufficient for my needs. Simon Hibbs --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
