WarcraftRealms.com

Hey guys,

My character located at http://warcraftrealms.com/char/79900499 is giving me a 'basic' (times new roman, black on white page) saying:

Error => Unable to query on line: 24 of /home/wrlogin/html/lib/CharacterData2.php

After some waiting the page loads fully but without his race (night elf), class (hunter) and level.
He's in a series of character history.

Transfers in chronological order:

1. Narlash (Emerald Dream - original character)
   Marked as a transfer and linked to:
2. Sequorian (Feathermoon)
   Marked as a transfer and linked to:
3. Sequorian (Emerald Dream - The character that should be displayed on http://warcraftrealms.com/char/79900499)

You need to be careful when editing your character the system isn't set with much user protection.

I am seeing
Milix (Feathermoon) transferred to Milix (Emerald Dream)

I am seeing
Narlash (Emerald Dream) transferred to Unknown character name ID# 79900499
AND
Sequorian (Feathermoon) transferred to Unknown character name ID #79900499
this is clearly an error.. as two different characters can't be merged.

I am seeing
Nordehn (Emerald Dream) transferred to Krevyk (Emerald Dream)

I am currently trying to find the data record for 79900499 so I can re-connect or reinsert the missing data. But the data is in the biggest table with 72 million rows of data.. so it will take time.

And as I was afraid.. the main data for record 79900499 having been corrupted was removed by the system.

I found record http://www.warcraftrealms.com/charsheet/202492531
which was created the next time Sequorian (Emerald Dream) was spotted.

I have reset the link to show Narhash(ED) to Sequorian(Fm)...
You need to claim the new Sequorian(ED)
BUT DO NOT do a transfer link!!.. I will see if I can either
recreate the 79900499 (doubtful) or transfer the history data from that ID to the new ID

assuming I can figure out which table(s) hold the data and where the link pointers are.

Cool! I really appreciate your continuous hard work bringoutyourdead!

Hours and hours of work... I don't think I will be doing this again...
since it was only a few entries.. I thought it would be worth the try.

I have updated the data such that the old 0499 records are now attached to 2531..
however in the process I am seeing 2 extra bogus records.. this might just be a caching issue.

The problems are 285 million entries... which Metalbeast decided had to be split across a number of joined tables to get the individual table size down to something reasonable for process speeds.

on updating the level 75 entry I believe it and one of the level 70 entries acted like they had jumped to a different subset table in ram memory.
I will let the system do its processing.. and see how things look tomorrow.