2013-05-05, 00:51
Team,
I found a problem in the code / db.
As is today the different names for the images (for example poster) are check boxes. This means that I can enable MULTIPLE saves for the same image (for example poster.jpg and poster.tmb)
The issue I discovered is that in the DB the field Poster is a single string! this means that we do not save all the images saved but the last one hardcoded in
It does return the LAST
This is not very good.
Now there are some options:
I'm in favor of option 1 or 2, option 3 will lead to quite a mess and also Ember does not show more than 1 poster and is not really useless.
what you advise?
is it useful to save multiple times the same image?
Question n.2
Does anyone use the local cache?
I found a problem in the code / db.
As is today the different names for the images (for example poster) are check boxes. This means that I can enable MULTIPLE saves for the same image (for example poster.jpg and poster.tmb)
The issue I discovered is that in the DB the field Poster is a single string! this means that we do not save all the images saved but the last one hardcoded in
Code:
Public Function SaveAsPoster(ByVal mMovie As Structures.DBMovie, Optional sURL As String = "") As String
It does return the LAST
Code:
strReturn = tPath
This is not very good.
Now there are some options:
- leave it as is as is not a major issue
- convert all the checkboxes into radio buttons, meaning the image will only be saved once
- check if possible to save in the db multiple paths for the same image
I'm in favor of option 1 or 2, option 3 will lead to quite a mess and also Ember does not show more than 1 poster and is not really useless.
what you advise?
is it useful to save multiple times the same image?
Question n.2
Does anyone use the local cache?