Hello!
If you use the "Char History" it will find more than one specify Chars, that identical, by example:
http://www.warcraftrealms.com/search.ph ... it1=SEARCH
There are viewed 5 times "Juleth", but it is always the same charakter in the same guild.
Char History, found more than one indetical Char
-
bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
This is a known somewhat random problem for some EU realms.
The source of the problem was the data submissions from people using the Russian client while using the CensusPlus addon on EU realms not listed as Russian language realms.
The problem is that when Rollie the original creator/owner of Warcraftrealms.com designed the database to store all of the uploaded data, he made certain design decisions that while correct for the times turned out to be less then perfect when Blizzard expanded the access to more languages.
When Metalbeast the current owner of Warcraftrealms.com and I realized why bad data was getting into the database we implemented more blocks to insure no more bad data would be processed.
But damage was already done.
I spent considerable time and effort in cleaning out obvious bad data, but I know that like with Juleth, some bad data still existed.
The processing of the problem uploads ended with three possible outcomes.
Upload processing died quickly and no data was imported.... GOOD
Upload processing created a new character record but then failed to add data to the other tables associated with characters ... NOT GOOD.. but not real bad.. two Juleth's from your search were these records.
Upload processing created a new character record and added the data to associated tables... VERY NOT GOOD .. the remaining two redundant Juleth's were in this status.
I have cleaned up the Juleth records.
You will only see the valid record now.
However there still is an issue with the data for that character.
There are multiple level 90 entries were no selection criteria was changed... this should not have happened.
Due to the database design, cleaning these entries out is a non-trivial task.. so it will not get fixed.
And to be very honest, I would not have done any of this clean out if it were not for the fact that my computer is tied up doing some long term near 100 percent CPU data processing.
I barely have spare cycles to run this browser with graphics turned off.
It is bad enough that my machine is tied up for about an hour on each run.. heaven forbid I try something like playing WOW..
or my main task might not get finished in the eight hours I have today.
The source of the problem was the data submissions from people using the Russian client while using the CensusPlus addon on EU realms not listed as Russian language realms.
The problem is that when Rollie the original creator/owner of Warcraftrealms.com designed the database to store all of the uploaded data, he made certain design decisions that while correct for the times turned out to be less then perfect when Blizzard expanded the access to more languages.
When Metalbeast the current owner of Warcraftrealms.com and I realized why bad data was getting into the database we implemented more blocks to insure no more bad data would be processed.
But damage was already done.
I spent considerable time and effort in cleaning out obvious bad data, but I know that like with Juleth, some bad data still existed.
The processing of the problem uploads ended with three possible outcomes.
Upload processing died quickly and no data was imported.... GOOD
Upload processing created a new character record but then failed to add data to the other tables associated with characters ... NOT GOOD.. but not real bad.. two Juleth's from your search were these records.
Upload processing created a new character record and added the data to associated tables... VERY NOT GOOD .. the remaining two redundant Juleth's were in this status.
I have cleaned up the Juleth records.
You will only see the valid record now.
However there still is an issue with the data for that character.
There are multiple level 90 entries were no selection criteria was changed... this should not have happened.
Due to the database design, cleaning these entries out is a non-trivial task.. so it will not get fixed.
And to be very honest, I would not have done any of this clean out if it were not for the fact that my computer is tied up doing some long term near 100 percent CPU data processing.
I barely have spare cycles to run this browser with graphics turned off.
It is bad enough that my machine is tied up for about an hour on each run.. heaven forbid I try something like playing WOW..
or my main task might not get finished in the eight hours I have today.