Local Database Issues

  • Comments posted to this topic are about the item Local Database Issues

  • Great read.

    FYI, this bit should be '...surrounding its capture...' not '...surrounding it's capture...'

    Not database related but anecdotally I've heard Chrome has a bad habit of thrashing the user's local drive also..

  • Sometimes it does feel that some companies only start to value their data when they realise they can sell it on. Not even when they are generating income via its use does it appear to be valued, in general.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

  • Same thing happens in gaming. Some people have claimed companies will install monitoring programs on your machine along with the game client (or part of the client) to check to see if you are using malicious programs to hack or exploit the game. These are done without your knowledge in some cases and send information back to the company so they can identify you and ban you from the game. While it's for the good intentions of all players who are playing the game, it's still doing this without your full knowledge.

  • It is alarming to think that Spotify could (inadvertently or even willingly) fill the hard disk of 40 million users worldwide.

    However, this can be mitigated by setting "Maximum Database Size" limit on the SQLite database named Mercury.db.

    https://www.sqlite.org/limits.html

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply