Reply to thread

Message

I think I may have a way to speed up scanning that is also flexible. As I mentioned above, when you scan for the first time (movie info data not in the database) and there are conflicts, you choose which title you want data for and the scan process goes and gets the data and populates movie info. When you select the title, the internal processing sets up an object (IMDBUrl) that contains the information required to scan for that title - like which database to get the title from (e.g. TI_MDB).

I was thinking that if we store that IMDBUrl in the database for that movie, then, when we do a refresh, the scan can bypass all of the selection process and get the data. At the same time, you can choose to fetch actor data if you want. When you want to change the title for a movie you already have in the database, then use Lookup to get the data for that single movie.

Does that sound like a plan? I think it addresses all scenarios and will be a lot faster. BTW, since I have made fetch actors optional, the scan process is 100's of percent faster.

<blockquote data-quote="Anthony Vaughan" data-source="post: 1286889" data-attributes="member: 153283">I think I may have a way to speed up scanning that is also flexible. As I mentioned above, when you scan for the first time (movie info data not in the database) and there are conflicts, you choose which title you want data for and the scan process goes and gets the data and populates movie info. When you select the title, the internal processing sets up an object (IMDBUrl) that contains the information required to scan for that title - like which database to get the title from (e.g. TI_MDB).I was thinking that if we store that IMDBUrl in the database for that movie, then, when we do a refresh, the scan can bypass all of the selection process and get the data. At the same time, you can choose to fetch actor data if you want. When you want to change the title for a movie you already have in the database, then use Lookup to get the data for that single movie.Does that sound like a plan? I think it addresses all scenarios and will be a lot faster. BTW, since I have made fetch actors optional, the scan process is 100's of percent faster.</blockquote>

[QUOTE="Anthony Vaughan, post: 1286889, member: 153283"] I think I may have a way to speed up scanning that is also flexible. As I mentioned above, when you scan for the first time (movie info data not in the database) and there are conflicts, you choose which title you want data for and the scan process goes and gets the data and populates movie info. When you select the title, the internal processing sets up an object (IMDBUrl) that contains the information required to scan for that title - like which database to get the title from (e.g. TI_MDB). I was thinking that if we store that IMDBUrl in the database for that movie, then, when we do a refresh, the scan can bypass all of the selection process and get the data. At the same time, you can choose to fetch actor data if you want. When you want to change the title for a movie you already have in the database, then use Lookup to get the data for that single movie. Does that sound like a plan? I think it addresses all scenarios and will be a lot faster. BTW, since I have made fetch actors optional, the scan process is 100's of percent faster. [/QUOTE]