It's an issue, nobody wants data that automatically deletes itself infesting their master database that contains billions of records, it's a bad process
If that method is so bad, then why do they do it all the time for time-limited POI's with no noticeable impact on the game's performance or stability?
that's why CMDR data is all kept separately in a linked database, if something goes wrong it's much easier to fix because you dealing with a much smaller database potentially only one CMDR's data records.
So, you mean like the list of assets owned by each CMDR (e.g. their ships, their stored modules, their engineered components,
and the individual stats assigned to each engineered component, list of explored systems and bodies, etc...)? What do you think they do with all the exploration data a commander has acquired when they die? They delete it, right? Or what about when a player deletes a stored module? Or sells a ship?
Given the verifiable examples of this happening already, why do you think adding
1 extra data value per CMDR (datestamp and system ID) would really make that much of a difference to the overall database performance?
No-one wants the entire game to go down because player X's data black box expired at the wrong time or didn't get created at all and the master database needs to be manually updated.
Please can you explain using your knowledge of database architecture (and, specifically the database architecture used for Elite Dangerous itself) exactly why you think this would have a noticeable detrimental impact on game stability and performance?
It's possible I'm overlooking some crucial detail, so I (and probably others here) are keen to hear your explanation.
You should go post on one of the threads where people are calling for 'more risks for explorers' - they need some balance.
