Hi there,

first of all... sry for my poor english. I'm german.

My Problem is that similar names were overwritten in the Database.
For example: My main char is "Leif". As Alt/Twink i've got a Shaman named "Leíf". If i upload the Guild- and characterprofile only one char is written in the database, the other doesn't exists anyway.

Some ideas?

MFG bandicut

Better yet :

I have a main char named Nowwhat
And a second one : Nowwhät
Used the second one for testing purposes - because this overwriting happend before : http://www.wowroster.net/Forums/viewtop ... wwhat.html
Back then, I couldn't find any overwriting happening to my char's.
Now, Nowwhat (updated first) is being overwriten by Nowwhät. I had to /deguild the sucker to make my main being updated.

This was never solved in that forum
Anyone able to debug this?

Will dive into it with the usual echo .... statements this evening (GMT+1 over here, meaning in 12 hours).

The thing is, my Nowwhät is deguilded, and few Officers present these days - and one can't guild an off line character.
Once he's in I'll go down back to SQL row-level if needed.
We'll see if separated ID are attributed.

What I did remember when seeing the upgrade log from before yesterday that a first char (the normal type) was recognised and it's stuff was loaded, the second (the ä type) was recognised - and loading.
In the V2 Roster, Nowwhat was marked yellow, but not ONE detail.
Nowwät is a small char. it had some fields filled up (it's still a lvl one 'no, stuff, no proffesions).

The test roster is over here: http://www.papy-team.fr/roster_20b1/ind ... emberslist

Got the same problem.

I change the collation in the table 'roster_members' for the field 'name' from 'utf8_general_ci' to 'utf8_bin'

Now similar names are displayed and not overwritten. Have to keep an eye of this if it's working correctly.

Paxton wrote:I change the collation in the table 'roster_members' for the field 'name' from 'utf8_general_ci' to 'utf8_bin'.

This actually 'solved' it....

But in ther mean time, I upgraded and lost track of the problem.
Be back in this one... because I do accept the solution 'as is' but hate to work on issues that could be web-server dependant.

I'll put it back - fool arround with my two character Nowwhat & Nowwhät - and update again.

I'll be back on this one if I see anything suspected.

Bump, because I want the other devs to look at this as well

First of all, please close my other thread, haven't seen this one here.

Turning to utf8-bin is not a good idea. this solves the problem with a and ä, but it is not case sensitive as a key and name is as key in roster_members and roster_players. so POETTER would be the same as poetter.

I tried out different utf8 and latin collations and they have all there stumbling blocks.

What would do the trick is to urlencode the names, with the disadvanges that we wont have mysql side sorting and everyone fetching data from this tables needs to urldecode the names.

Crappy stuff

BTW: a=ä=â=á=à=A=Ä=Á=À=Â *rofl*

One stupid question .. where is the problem with case insensitive ?

Because Blizzard don't allow the case sensitive to make another char...

Subxero subxero and suBXero are the same character on wow.

But...

Aldor, äldor and áldor are DIFFERENT sure!

Thats right

You can search on armory characters like:

http://eu.wowarmory.com/character-sheet ... n&n=Radgar
http://eu.wowarmory.com/character-sheet ... n&n=RADGAR
http://eu.wowarmory.com/character-sheet ... n&n=RaDGaR
http://eu.wowarmory.com/character-sheet ... n&n=rAdgAr
http://eu.wowarmory.com/character-sheet ... n&n=RadgaR

And ever get the same results...