StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSpree Commerce Image (Asset) Associated with multiple OptionValues
primarykey
Id
20435200
data
AcceptedAnswerId
20673772
AnswerCount
2
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-12-06T23:07:23.833
FavoriteCount
0
LastActivityDate
2013-12-19T05:00:08.320
LastEditDate
LastEditorUserId
0
OwnerUserId
998352
ParentId
0
PostTypeId
1
Score
1
ViewCount
770
LastEditorDisplayName
text
Body
I'm wondering what the best practice is for setting up a relationship as follows. Currently, Spree offers the following models and associations. asset.rb <pre><code>module Spree class Asset < ActiveRecord::Base belongs_to :viewable, polymorphic: true, touch: true acts_as_list scope: :viewable // .... end end </code></pre> image.rb (perhaps this is irrelevant, but inherits from asset model) <pre><code>module Spree class Image < Asset // ....... end end </code></pre> variant.rb <pre><code>module Spree class Variant < ActiveRecord::Base has_and_belongs_to_many :option_values, join_table: :spree_option_values_variants, class_name: "Spree::OptionValue" has_many :images, -> { order(:position) }, as: :viewable, dependent: :destroy, class_name: "Spree::Image" // ...... end end </code></pre> option_value.rb <pre><code>module Spree class OptionValue < ActiveRecord::Base belongs_to :option_type, :touch => true acts_as_list scope: :option_type has_and_belongs_to_many :variants, join_table: 'spree_option_values_variants', class_name: "Spree::Variant" // ...... end end </code></pre> Currently, when an image (asset) is added to a product variant, a single db row is added to the spree_assets table. This is desired. Within the spree_assets table is a column called viewable which holds the id of the variant. This isn't extremely flexible. Basically, this means that a single image can only be applied to a single variant. Currently the Spree Admin reflects this as well. When uploading a product image, a select box is provided to select a single variant to apply this image to. This could be fine for many stores, but for our store, a Green T-Shirt image should apply to Small, Medium, and Large Green T-Shirts. Proposed Solution I have detailed the proposed solution in a <a href="https://docs.google.com/document/d/1q2Xke3BoSxVMKPfVTtvhpVkTa-lpWtdyFfSizCPcg5s/edit?usp=sharing" rel="nofollow">Google Doc</a>. Basically, I'm thinking a new table should be used. This new table would hold foreign keys for the asset, option_value, and variant. This could certainly be completely wrong, but that's why I'm posting here. :) Should I create this new db table? Or, are the relationships currently in place to accommodate my needs? If I do create a new db table, would I need a join model? What should it look like? This may be too abstract for Stack Overflow, and if so, I apologize. Please PM me if you'd simply like me to hire you to carry out the implementation.
Tags
<ruby-on-rails><spree>
Title
Spree Commerce Image (Asset) Associated with multiple OptionValues
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJarrod
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThis kind of question is probably better asked on the Spree mailing list: https://groups.google.com/forum/?hl=de#!forum/spree-user
 singulars
 PostPostId
 POSpree Commerce Image (Asset) Associated with multiple OptionValues
 UserUserId
 USAlexander Presber
2. COThat's where I stared, but didn't get far. For now, I've hired a Rails Developer for help. Will open source the implementation when closer to completion.
 singulars
 PostPostId
 POSpree Commerce Image (Asset) Associated with multiple OptionValues
 UserUserId
 USJarrod

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.