Archive > AO 0.6 support

Server merge!

(1/6) > >>

crocks:
Hey everyone,
according to planning server merge at the end of 2012 (as it seems). What would be the main thing on Bebot to be able to keep the databases and all around it if the character ID will be wiped and every character will get a new ID. Bebot works mostly with Char ID as you know.

Are there any plans how to transfer the databases and bots itself to the new server with current informations the databases have? (Account informations - points, raids done, raids history, raffle history, auctions history, character alts, character permissions etc etc etc ... )

Thanks

/CR

Shelly:
I have been pondering the same thing... The way I came up with is very manual and tedious...

1. export your current DB to a flat file
2. after merge... look up all the names for the new character ID
3. hand edit the export you did in step 1 updating the character IDs for every member/guest in the DB to the new #
4. re-load the database with your edits and restart your bot.

Not a pretty solution... but I am not a coder by nature or occupation. :)

Shelly

Glarawyn:
What we should probably do is add some bridge tables.

BeBot Accounts:
AccountID - Unique account ID number generated by BeBot.
OldCharacterID - Premerge Character ID.
NewCharacterID - Postmerge Character ID.
OldCharacterName - Character Name
NewCharacterName - New/Current Character Name.

I'm making the assumption that some characters will get renamed due to name collisions on RK1 and RK2.

Second Bridge Table: Alt Registration using AccountID. Associate ChacterIDs (or Character Names?) with BeBot AccountIDs. 
AccountID - Foreign Key.
OldCharacterID - Only needed until merge, then it should be blank for new registrations.
NewCharacterID - New/Current Character ID. Populated after merge.
Composite Primary Key: AccountID, CharacterID.

Third Bridge Table: Display Names. 
AccountID - Foreign Key.
DisplayName - Display name for account. This would Default to the main character. Add setting to allow users to provide a custom name that does not match an AO character if they desire.


Then we need some logic for dealing with remapping IDs, looking up Alts/Mains using the new system, etc. 

Zweiblum:
so... are there any "To-Dos" for PhP newbs like me to keep the bots running after merge?

Glarawyn:

--- Quote from: Zweiblum on January 08, 2013, 11:41:59 am ---so... are there any "To-Dos" for PhP newbs like me to keep the bots running after merge?

--- End quote ---

Find a sufficient bribe to get a BeBot coder to fix it?  :P

Navigation

[0] Message Index

[#] Next page