Team Drizzle, and Jay..
OK, so it looks like the problem doesn't have to do with grants, but
is isolated to working with Unix domain sockets (as opposed to TCP
port). Drizzle itself does not support Unix domain sockets, but I'm
not sure whether libdrizzle has also dropped support for it. I've
pinged Eric Day for an answer. Regardless, though, there should be
more of a descriptive message than "could not connect" ;)
Both issues exist, socket and auth.
No, I think it is both lack of support for domain sockets is issue 1.
No big deal once I know that I can workaround.
Issue 2 is authentication failure..
I was unable to get authentication against MySQL with the drizzle
console in any way.
I quoted password, unquoted passwords. etc.
If I get back to this today, I will capture the TCP traffic and see
what the drizzle console does with my password and why MySQL does not
agree with it.
My Mysql version of course _might_ having something to do with it, but
I thought authentication had stabilized about 5 years ago.
mysql> select version();
+----------------------------------+
| version() |
+----------------------------------+
| 5.1.35-ndb-7.0.7-cluster-gpl-log |
+----------------------------------+
1 row in set (0.00 sec)
Thanks
--
Tom
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
