Yesterday I was caught out with said protocol changes, and I voiced my initial lack of understanding concerns on IRC.
I think this is a valid end user case you should consider in your back and forth on this topic. So I want to eval Drizzle as a separate product, and for my test case I'm going to install Drizzle on my test server. My test server already has multiple versions and instances of MySQL running, including on the DEFAULT MySQL port of 3306 I install Drizzle, however I can't start it. I get an obtuse error message. sbin/drizzled & [1] 6633 Listening on :::3306 bind() failed with errno: 98Do you already have another drizzled running?Aborting 100312 14:53:16 InnoDB: Starting shutdown... 100312 14:53:17 InnoDB: Shutdown completed; log sequence number 97254 [1]+ Exit 1 sbin/drizzled What the? I like other users may want to test out Drizzle. What I find now is twin protocols and the need to be FORCED to specify --mysql-protocol-port=3399 Not withstanding the political or other commercial reasons for now providing this backward compatibility and 3306 overloading, I'm not really wanting to discuss the pros/cons of this in this response. What I want to discuss is WHY this is the default enabled situation. I'm testing Drizzle in isolation. I would expect that providing MySQL compatibility to be a value add? feature not a required dependency This is just my .02 cents worth from an external user perspective and observation. Goes to show the last time I started up drizzled, my previous still running version BTW didn't have this new protocol dependencies. Ronald On Tue, Mar 9, 2010 at 6:24 PM, Eric Day <[email protected]> wrote: > Hi everyone! > > A branch just hit trunk that changes the default testing and client > tool port to 3306 (the official MySQL port), which is compatible with > the MySQL protocol. This change is being done so we have a stable > port to continue using while the new protocol is being developed > on 4427 (the official Drizzle port). All the client tools (drizzle, > drizzledump, ...) also default to using the MySQL protocol mode in > libdrizzle now. > > Drizzle will still listen 4427 for the time being, but it is suggested > to start using port 3306 for all communication with the server. The > protocol behind 4427 will start to change sometime in the future, > and at that point current tools and clients will need the latest > client libraries to communicate with it. I'm going to be updating > libdrizzle to also default to 3306 in MySQL mode, so any drivers > out there today built on libdrizzle will also get the update. As > new protocol development begins, using it will require a special > experimental libdrizzle connect flag that will be created. > > If you run into any issues with this change, please let us know by > filing a bug. :) > > Thanks! > -Eric > > _______________________________________________ > Mailing list: > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
