Datamapper ORM Multi-tabel Relationship Halp!

[eluser]Genki1[/eluser]
Your idea of Purchases "has one" Option is throwing me off because there are multiple Options applied to each Template. Maybe my scenario is not clear. Here's what I'm doing:

A User purchases a Template.
There is a library of 15 configuration settings (I called them "Options" in my posting here).
Several of the config settings are automatically applied to the Template and are set with a default value which the user can change. (Note: user purchases only the Template, not the config settings/options.)

Example of two purchases:

User "Joe" purchases the "Blue Sky" template. Ten of the 15 config settings are automatically applied to the template and each setting is loaded with a default value.

User "Harro" purchases the "Gentle Valley" template. Twelve of the 15 config settings are automatically applied to this template and loaded with default values.

Code:

User: Joe
Template: Blue Sky
Config settings:
[option_id] [option_name]     [value]
  1           Font              Arial
  2           Background color  Blue
  3           State             California

Code:

User: Harro
Template: Gentle Valley
Config settings:
[option_id] [option_name]     [value]
  1           Font              Helvetica
  3           State             Hawaii
  5           Position          Center
  6           Foreground image  Sunflowers

So, as in my earlier post, I envision my "Purchases" table looking like this:

Code:

[id] [user_id] [template_id] [option_id] [value]
  1       1         1             1        Arial
  2       1         1             2        Blue
  3       1         1             3        California
  4       2         7             1        Helvetica
  5       2         7             3        Hawaii
  6       2         7             5        Center
  7       2         7             6        Sunflowers

Based on this, how can Purchases be "has_one" to Options?