On Sat, Jan 14, 2006 at 04:51:44PM -0700, Peter Michaux wrote:
> Option 1 - would have many join tables and each would require a class in my
> ORM.
>
> categories_images
> - category_id
> - image_id
>
> images_products
> - product_id
> - image_id
>
> Option 2 - have a one generic join table and
Hi,
I have tried two db designs and both can work but I wonder which one
the db gurus would go with. This is a general db design question
that has cropped up in a few situation. Here is the example I've been
working on...
In an online store, categories and images have a many-to-many relationship
