Note that there are some explanatory texts on larger screens.

plurals
  1. USFaddishWorm
    primarykey
    data
    text
    plurals
    1. CO(1) No, only some things will be kept in history - and I database those in seperate tables through tomcat. (2) No history for config data is needed. (3) Yes there is commonality, in that each system will have most of the config keys, only the values will change in the key-value pairs. (4) 100 times a second may be an over-estimate, but If I aim to satisfy that then I know the server will stand up to almost anything.
      singulars
    2. COI have been using it for years, but I use ext2js and it isn't set up properly. I use notepad++ And debug bar to trace, if you have non-minified code you can usually see the offending javascript. Although I would love to know if there is a better way.
      singulars
    3. COI hadn't heared of memory tables before - they sound like a great solution to keep track of the current state. The current state is a list of unique song identifiers that make up a playlist. As songs play, the playlist changes so the state changes. There are other things that make up the current state like volume level for example. These need to be accessible at all times, and will change frequently. I think it is a great idea what you have posted, in that each configuration value will have its own entry, but with posttime as part of the primary key, is it possible to still do updates?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload