This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| softwares:giocoso:promenu:proinitdb [2025/12/04 18:07] – hjr | softwares:giocoso:promenu:proinitdb [2025/12/04 18:08] (current) – hjr |
|---|
| |
| That's music playing locally, because the global Pro database told the local machine what to play next: basically, once the global database has been initiated, it acts as both 'source of information about what recordings to play' and 'repository of data about what recordings have been played'. | That's music playing locally, because the global Pro database told the local machine what to play next: basically, once the global database has been initiated, it acts as both 'source of information about what recordings to play' and 'repository of data about what recordings have been played'. |
| 3.0 Summary | |
| |
| | ===== 3.0 Summary ===== |
| Initialisation of a Pro database is a once-off affair, performed by the client Giocoso device that has been declared to be 'primary' in the Administration menu, Option 2: Create or Edit the Configuration file. It involves creating various tables and views in the Pro database, then copying across data from the local recordings and plays tables to become the contents of the global_recordings and global_plays tables. Once you've initialised the Pro database, it can be used by all Giocoso client devices to know what can be played and what has been played. | Initialisation of a Pro database is a once-off affair, performed by the client Giocoso device that has been declared to be 'primary' in the Administration menu, Option 2: Create or Edit the Configuration file. It involves creating various tables and views in the Pro database, then copying across data from the local recordings and plays tables to become the contents of the global_recordings and global_plays tables. Once you've initialised the Pro database, it can be used by all Giocoso client devices to know what can be played and what has been played. |
| |