What's the standard practice for naming an intermediary table in SQL?

Question

I have a table called Product and a table called Shop. Each shop has a list of Products that it sells. I need an intermediate table that has ShopID and ProductID in it. What should I call that table? My mind has drawn a blank.

ShopProducts?

Edit: Perhaps I should call it "ShopAvailableProducts"? Or is that too confusing.

Answer 1

Yes ShopProduct (depending on the plurals you use) would be how I'd name a link entity.

Shop
  |
-----
| | |
ShopProduct
| | |
-----
  |
Product

So a shop can have many products and each product can be sold in many shops

Answer 2

I prefer something along the lines of ShopProductsJunction. This article might give a few other naming hints:

...also known as a cross-reference table, bridge table, join table, map table, intersection table, linking table, or link table

Answer 3

Yes, ShopProducts is good enough. No problem with that

Answer 4

Personally I would just use ShopProduct as it makes sense in my language a product for/from/asociated-with a shop.

Answer 5

Shop2Product (or Product2Shop) is better: "2" in mid shows that this is intermediary table.