Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
softwares:giocoso:dbmenu:fullscan [2025/11/19 19:35] – hjrsoftwares:giocoso:dbmenu:fullscan [2025/11/19 19:36] (current) – hjr
Line 49: Line 49:
 All fast (and full) refreshes of Giocoso are updates to the Giocoso //local// database only, by default. Each installation of Giocoso on different music-playing computing devices will have its own, unique database, periodically refreshed and kept accurate by separate fast or full refreshes. All fast (and full) refreshes of Giocoso are updates to the Giocoso //local// database only, by default. Each installation of Giocoso on different music-playing computing devices will have its own, unique database, periodically refreshed and kept accurate by separate fast or full refreshes.
  
-However, the release of Version 3.30 introduced the concept of 'Giocoso Pro', whereby a device's //local// database contents can be 'pushed' to a remote MySQL/MariaDB database that is shared amongst all music-playing devices. Accordingly, from that version onwards, and **//if//** Pro functionality has been enabled by setting a remote database server's IP address in the Giocoso configuration file, a fast refresh will complete its local work by going on to copy the refreshed local RECORDINGS table to the remote shared database. Essentially, the local RECORDINGS table's data is inserted into the remote database's GLOBAL_RECORDINGS table.+However, the release of Version 3.30 introduced the concept of 'Giocoso Pro', whereby a device's //local// database contents can be 'pushed' to a remote MySQL/MariaDB database that is shared amongst all music-playing devices. Accordingly, from that version onwards, and **//if//** Pro functionality has been enabled by setting a remote database server's IP address in the Giocoso configuration file, both a fast //and// a full refresh will complete its local work by going on to copy the refreshed local RECORDINGS table to the remote shared database. Essentially, the local RECORDINGS table's data is inserted into the remote database's GLOBAL_RECORDINGS table.
  
 This data copying process is //always// a complete **replacement** of the GLOBAL_RECORDINGS table contents. It starts by deleting all rows from that table and then re-loading it from scratch. In this way, the GLOBAL_RECORDINGS table always contains up-to-date data about the recordings that the device doing the full refresh can (and can no longer) see. This data copying process is //always// a complete **replacement** of the GLOBAL_RECORDINGS table contents. It starts by deleting all rows from that table and then re-loading it from scratch. In this way, the GLOBAL_RECORDINGS table always contains up-to-date data about the recordings that the device doing the full refresh can (and can no longer) see.
  • softwares/giocoso/dbmenu/fullscan.txt
  • Last modified: 2025/11/19 19:36
  • by hjr