Hi Alexandre

I have tested the performance and it is not too hot. On a basic test of
selecting all items with their stock level performance was

0.9s for the view vs 0.4s for a direct table SQL

not great but not too bad. However for a restricted select (just the
same details for one item) the results are

0.6s for the view and 0.015s for direct (note that the accuracy of the
timing app means that the fasted result possible is 0.015s, so it very
well could have been faster than that).

This is with 56000 records in stockLevel.

So the view is an easy solution but too slow :-(

Thanks for the suggestion anyway, I should have tested it earlier than this.

Rob

> Alexandre Benson Smith wrote:
>
>> I am not sure if I understood it well...
>>
>> But you could create a view to mimic a summary table, or even create a
>> table with details with another name, and create a view with the old
>> name of the table with just a sumary, you will have not to change a lot
>> of SQL.
>>
>> see you !
>>
>>
>>
> Hi
>
> I thought about a view but thought the performance might suffer. Will
> run some tests and see what the performance is like.
>
>
>