| Both sides previous revision Previous revision | |
| softwares:giocoso:dbmenu:fastscan [2025/11/19 12:48] – [4.0 Scheduling Fast Scans] hjr | softwares:giocoso:dbmenu:fastscan [2025/11/19 12:51] (current) – [5.0 Conclusion] hjr |
|---|
| |
| ===== 5.0 Conclusion ===== | ===== 5.0 Conclusion ===== |
| Fast Scans are relatively quick ways of adding <em>new</em> recordings into a Giocoso music database, and for pruning out old ones that no longer exist. They are, however, completely useless when it comes to updating the metadata associated with existing recordings, since fast refreshes see folders, not files ...and thus the metadata <em>within</em> a file can be changed as often as you like and the fast refresh process will never spot the alterations! | Fast Scans are relatively quick ways of adding //new// recordings into a Giocoso music database, and for pruning out old ones that no longer exist. They are, however, completely useless when it comes to updating the metadata associated with existing recordings, since fast refreshes see folders, not files ...and thus the metadata //within// a file can be changed as often as you like and the fast refresh process will never spot the alterations! |
| |
| Functionally, the way a Fast Refresh works is as follows: | Functionally, the way a Fast Refresh works is as follows: |
| <ul> | |
| <li>Produce a list of unique folder names already in the database</li> | * Produce a list of unique folder names already in the database |
| <li>Go off to the file system and produce a list of unique folder names from there</li> | * Go off to the file system and produce a list of unique folder names from there |
| <li>Compare the two lists</li> | * Compare the two lists |
| <li>If anything on the second list is not already in the database, those are 'new folders'</li> | * If anything on the second list is not already in the database, those are 'new folders' |
| <li>Visit every new folder discovered and add the metadata for the FLACs found there to the RECORDINGS table</li> | * Visit every new folder discovered and add the metadata for the FLACs found there to the RECORDINGS table |
| </ul> | |
| This is why <strong>folder</strong> name changes to existing recordings <em>will</em> trigger the addition of the newly-named recording to the database, whereas mere changes to <em>file </em>names or any metadata changes will not. | This is why **folder** name changes to existing recordings //will// trigger the addition of the newly-named recording to the database, whereas mere changes to //file// names or to metadata values will **not**. |