Both of your Tables must have a primary index field.
I usually name this autoindex
id.
To take your example
orders is your main table.
- id (index)
- customer_name (title)
- address
- ...
Now you have
orders_details.
- id (index)
- id_order (id of the order -> linked with id field in table orders)
- id_product (optional: id of the product -> linked with the product)
- product_name (title)
- price
- ...
It's a classical 1/N relation.
All you must do is to create a subtemplate and link "orders_details->id_order" => with "order->id". In your subtemplate you just write a how the output of a product-line should happen.
<table>
<tr>
<td style="width:80%">{joodb field|product_name}</td>
<td style="width:20%">{joodb field|price}</td>
</tr>
</table>
If the name of your subtemplate is "details". Write {joodb subtemplate|details} in the single entry template for your main table "orders"
In your case I would use a N/M relation. That means your order_details table would only be an index linking between your products and the order.
- id (index)
- id_order (id of the order -> linked with id field in table orders)
- id_product (id of the product -> linked with the product)
Then you are able to print out product-images, product-details and links to the product view.
Products would be your linked table and orders_details your index-table.
To be honest. Joodb is not made for a shop system. A real shop system is much to complex.
