2012-09-25, 13:35
I can understand the reasoning, but I can hardly understand that this vision degrades performances to the point of being unusable.
Once again, the problem we have is limited to thumbnails in lists.
I can hardly see the point of fetching the fanarts, cleararts, logos, ... in lists of e.g. movies. Those should be limited to "Details" fetching.
OTOH, thumbnails are here forever, will be requested forever in basically 99% of all item lists fetched from the DB and basically have a 1-to-1 relationship with their associated entities.
So, if adding a "thumbUrl" field to the tables is not acceptable (which I disagree with, again specifically for thumbnails), adding the JOIN to the thumbnails in the DB views once and for all will keep the vision while keeping performances. No need to add the other, "details" art, to the views.
Hehe, we are synchronized, here
Once again, the problem we have is limited to thumbnails in lists.
I can hardly see the point of fetching the fanarts, cleararts, logos, ... in lists of e.g. movies. Those should be limited to "Details" fetching.
OTOH, thumbnails are here forever, will be requested forever in basically 99% of all item lists fetched from the DB and basically have a 1-to-1 relationship with their associated entities.
So, if adding a "thumbUrl" field to the tables is not acceptable (which I disagree with, again specifically for thumbnails), adding the JOIN to the thumbnails in the DB views once and for all will keep the vision while keeping performances. No need to add the other, "details" art, to the views.
(2012-09-25, 13:21)Tolriq Wrote: In the mean time new needs have surfaced for more arts that skins have hacked and Xbmc tries to get into (cdart, ....), and the way that was chosen is good, but it the cost that is associated with it is way too much for the thumb part.
Hehe, we are synchronized, here