Re: lost mysql root password

On Friday 03 March 2006 17:08, anoop aryal wrote:
On Friday 03 March 2006 03:12 pm, Matt Price wrote:
do:

select hex(User) from user where User LIKE 'root%';


that should give you the hex values of the characters that are
there.

have all four. I guess there must be some white space in the
username somewhere. Is there an easy way to identify the
precise value of a mysql field (e.g. by dumping to a CSV file)?
I'd like to try to figure

+----------------------------------+

| hex(User) |

+----------------------------------+

| 726F6F74 |
| 726F6F74202020202020202020202020 |
| 726F6F74 |
| 726F6F74202020202020202020202020 |

+----------------------------------+
4 rows in set (0.00 sec)

Is that even encoded at all? That looks a bit like it would say
"root ", twice, in ascii to me. Look it up in an ascii table
for old 7 bit ascii stuff to be sure.

thanks anoop! I guess those 02's are spaces then... Looks like
most of the user lines from my old db are corrupted in this way as
well. wierd.

Not 02, but $20's, eg an ascii space char.

i would check the encoding being used vs. the encoding that was used
when it was initially created. it sounds like you were using a
wide_char encoding (eg. UTF-8) before and somehow has now reverted
back to latin-1 or some other single char encodings. i'm not an
expert on encodings etc.. know just enough to be dangerous. but if
this is database wide, (look at char/varchar/text fields and they
should all display this behavior), this is encoding related. on a
wide char encoding (say utf-8), the database reserves multiple bytes
per char not knowing what char it will need to save there. when you
tell mysql that it's not wide char, it will just show you what it has
- including the previously reserved bytes. it's odd that it's using
x20 to pad data tho.

or something like that.

Thanks much for your help!

matt

--


anoop
aaryal@xxxxxxxxxxxxxxxx

--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: lost mysql root password
    ... On Friday 03 March 2006 03:12 pm, Matt Price wrote: ... i would check the encoding being used vs. the encoding that was used when it ... single char encodings. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: lost mysql root password
    ... On Friday 03 March 2006 04:38 pm, Gene Heskett wrote: ... Not 02, but $20's, eg an ascii space char. ... this is encoding related. ... the database reserves multiple bytes ...
    (Debian-User)
  • Re: Need help on string manipulation
    ... unlike characters using char, which may use a multibyte encoding. ... If any unicode char can be encoded in a single ...
    (comp.lang.c)
  • Re: Send string to IP address
    ... to char variables, but I'm not sure if this is feasible ... The relevant ANSI codepages specify glyphs for each byte value. ... The characters whose byte values are in 128-255 are not guaranteed to map to U+0080-U+00FF, though, and often don't. ... The only encoding that's going to be compatible with that point is the trivial one whose operations are ...
    (comp.lang.java.programmer)
  • Re: WCHAR conversion problem
    ... and I'm using an API with WCHARs... ... The times where you could assume that a char* is just a char* in terms of an ASCII string are long over. ... The multibyte encoding from the mb* string functions is only one of many. ...
    (microsoft.public.vc.language)