This weekend I was very busy with OS CCK and tried many things. Please don't be angry if I list a few suggestions for improvement or requests that would make the backend management of a reservation considerably easier.

1)
Might it not be better to store all the reviews in a seperate table than to put them into the same table where are all the rental requests and orders (os_cck_content_entity#)? In my opinion it would be much clearer.

Hi

This created as created, every propose have good and bad sides.
May be we all little know assembler language but very less people agree create all programs with it. We wish at end have so product - where client who know Word, may easy create website with help our CCK. So so clients no need know our tables structure.

In Our Joomla cck every entity has many fields, but for best performance we need these fields connect to so less tables as we can, we use 2-6 tables for save 1 Entity (depend of fields which you use)

But as result - you see we have a lot tables.

For review you may use so many fields as you need, for review you may create layouts exactly as for any other layouts, because of that we use for review same tables as for other Instance.

BUT, Now review - you may create as child Entity

Regards
OrdaSoft team