Ever notice that the Personal tab of Doff assignments shows the character's old name?
It seems that the rename token changes the data in one column in one table, but there must be multiple columns storing character name data.
And isn't that disturbing? I mean, this bug really obvious shows that their database has been created by someone not competent to do so. Who stores one name, belonging to one entity all over the place? Every 1st semester IT student knows this the one thing you must not do! It creates inconsistencies that can not be easily fixed..
I have the same rename problems most here describe and while reading trough your posts I realized that this bug will not be fixed soon and to be honest, it would really surprise me to see this bug ever being fixed.. like evar, evar. I am really sorry if this might come as a disappointment, but there is a reason why this bug had not been fixed by now and there is a reason why they won't even address this. I still hope filing enough bug reports about this helps getting this fixed someday, but think about this, they developed all the program code around this inconsistent database structure. I imagine they thought about all the stuff they'd have to change when this bug was brought to their attention, to get rid of this problem, realized that they not just had to redo the database structure, but also find and rewrite all the program code connected with this, looked at each other while shaking their heads and moved on. My bet is, that they would probably break the game when they try to fix this and I guess they know that and some decision maker decided that it's to risky and not worth it fixing this bug.
If is used a foreign key can be update by cascade. Anyway using strings as table key has always been a bad practice, even more if that string is subject to changes. I think they really need a db expert, those kind of errors are unacceptable for a game of this size.
Their references might not actually be declared as foreign keys. They might be using them like foreign keys, but haven't specified them as such, so it may not be clear which tables depend on the character name for reference.
And isn't that disturbing? I mean, this bug really obvious shows that their database has been created by someone not competent to do so. Who stores one name, belonging to one entity all over the place? Every 1st semester IT student knows this the one thing you must not do! It creates inconsistencies that can not be easily fixed..
I have the same rename problems most here describe and while reading trough your posts I realized that this bug will not be fixed soon and to be honest, it would really surprise me to see this bug ever being fixed.. like evar, evar. I am really sorry if this might come as a disappointment, but there is a reason why this bug had not been fixed by now and there is a reason why they won't even address this. I still hope filing enough bug reports about this helps getting this fixed someday, but think about this, they developed all the program code around this inconsistent database structure. I imagine they thought about all the stuff they'd have to change when this bug was brought to their attention, to get rid of this problem, realized that they not just had to redo the database structure, but also find and rewrite all the program code connected with this, looked at each other while shaking their heads and moved on. My bet is, that they would probably break the game when they try to fix this and I guess they know that and some decision maker decided that it's to risky and not worth it fixing this bug.
There are other bugs that seem suspiciously like the result of poor database design. You often see drops with the wrong stats or picture. Two items that should be identical have different stats.
There are other bugs that seem suspiciously like the result of poor database design. You often see drops with the wrong stats or picture. Two items that should be identical have different stats.
That is a good point, because I saw these bugs, too and immediately thought how could modifiers in the name or icon numbers, stats etc. not line up, EXCEPT if you store the data, attributes etc. several times, in different places, like one attribute ItemLevel for the name, one attribute ItemLevel for the icon number, one for the stats.. that's really sad, because you can destroy a good software with a flawed database design. Fixing something like this usually means rewriting the whole thing..
And please don't get me wrong, I am not the least interested in blaming Cryptic or making them look bad or something like that, I just want to enjoy a relatively bug free software.. which means in this case, when I buy a rename token, I expect it to work.. yeah, silly me :rolleyes:
Does anyone know why it's occasionally impossible to rename a boff? When I get one from the exchange and click 'join', the 'rename' button is often greyed out so I'm stuck with a randomly generated name, is there a work around to this?:(
[SIGPIC][/SIGPIC]
I'm not THAT difficult to please, I just have a very low tolerance threshold for stupid BS! - George Carlin.
Comments
We are aware of the issue, but it will take some time to fix.
And isn't that disturbing? I mean, this bug really obvious shows that their database has been created by someone not competent to do so. Who stores one name, belonging to one entity all over the place? Every 1st semester IT student knows this the one thing you must not do! It creates inconsistencies that can not be easily fixed..
I have the same rename problems most here describe and while reading trough your posts I realized that this bug will not be fixed soon and to be honest, it would really surprise me to see this bug ever being fixed.. like evar, evar. I am really sorry if this might come as a disappointment, but there is a reason why this bug had not been fixed by now and there is a reason why they won't even address this. I still hope filing enough bug reports about this helps getting this fixed someday, but think about this, they developed all the program code around this inconsistent database structure. I imagine they thought about all the stuff they'd have to change when this bug was brought to their attention, to get rid of this problem, realized that they not just had to redo the database structure, but also find and rewrite all the program code connected with this, looked at each other while shaking their heads and moved on. My bet is, that they would probably break the game when they try to fix this and I guess they know that and some decision maker decided that it's to risky and not worth it fixing this bug.
Their references might not actually be declared as foreign keys. They might be using them like foreign keys, but haven't specified them as such, so it may not be clear which tables depend on the character name for reference.
There are other bugs that seem suspiciously like the result of poor database design. You often see drops with the wrong stats or picture. Two items that should be identical have different stats.
That is a good point, because I saw these bugs, too and immediately thought how could modifiers in the name or icon numbers, stats etc. not line up, EXCEPT if you store the data, attributes etc. several times, in different places, like one attribute ItemLevel for the name, one attribute ItemLevel for the icon number, one for the stats.. that's really sad, because you can destroy a good software with a flawed database design. Fixing something like this usually means rewriting the whole thing..
And please don't get me wrong, I am not the least interested in blaming Cryptic or making them look bad or something like that, I just want to enjoy a relatively bug free software.. which means in this case, when I buy a rename token, I expect it to work.. yeah, silly me :rolleyes:
I'm not THAT difficult to please, I just have a very low tolerance threshold for stupid BS! - George Carlin.
My PvE/PvP hybrid skill tree
June 14th, 2014 and the problem persists.