search for: image_join

...1 - would have many join tables and require many join models. (The join models are to use the position field for acts_as_list to order the images) categories_images - category_id - image_id images_products - product_id _ image_id Option 2 - have a one generic join table and only one join model image_joins - owner_class - owner_id - image_id In option 2 a record could be (Category, 2, 3) or (Product, 4, 1) -------- Option 1 seems simpler but could lead to some repetitive code (at least in the data base definition). Option 2 is a little more complicated and I don''t know how it fits into...